mirror of
https://github.com/DopplerHQ/awesome-interview-questions.git
synced 2025-12-10 16:22:12 +00:00
Merge pull request #231 from DopplerHQ/rb/link-checker-action
Add link checker action
This commit is contained in:
Ryan Blunden
GitHub
commit
12ef5d080a
11
.github/workflows/link-checker.yml
vendored
Normal file
11
.github/workflows/link-checker.yml
vendored
Normal file
@ -0,0 +1,11 @@
|
||||
name: Markdown link checker
|
||||
on: [pull_request,workflow_dispatch]
|
||||
jobs:
|
||||
markdown-link-check:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@master
|
||||
- uses: gaurav-nelson/github-action-markdown-link-check@v1
|
||||
with:
|
||||
config-file: '.github/workflows/mlc_config.json'
|
||||
|
||||
44
.github/workflows/mlc_config.json
vendored
Normal file
44
.github/workflows/mlc_config.json
vendored
Normal file
@ -0,0 +1,44 @@
|
||||
{
|
||||
"ignorePatterns": [
|
||||
{
|
||||
"pattern": "https://adevait.com/android/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://www.fullstack.cafe/blog/docker-interview-questions-and-answers"
|
||||
},
|
||||
{
|
||||
"pattern": "https://www.fullstack.cafe/blog/5-graphql-interview-questions-you-should-know"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/ios/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/java/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/javascript-developers/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/nodejs/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/php/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://adevait.com/python/interview-questions"
|
||||
},
|
||||
{
|
||||
"pattern": "https://danielmiessler.com/study/infosec_interview_questions/"
|
||||
},
|
||||
{
|
||||
"pattern": "https://www.datacamp.com/community/news/top-100-data-science-interview-questions-cc3lts7gj5j"
|
||||
}
|
||||
],
|
||||
"timeout": "5s",
|
||||
"retryCount": 3,
|
||||
"fallbackRetryDelay": "10s",
|
||||
"aliveStatusCodes": [
|
||||
200,
|
||||
206
|
||||
]
|
||||
}
|
||||
@ -448,7 +448,6 @@ Please read the [contribution guidelines](contributing.md) or [creating a list g
|
||||
* [A list of Frequently Asked Questions and their answers, sorted by category](http://www.scala-lang.org/old/faq)
|
||||
* [A list of helpful Scala related questions you can use to interview potential candidates](https://github.com/Jarlakxen/Scala-Interview-Questions)
|
||||
* [How Scala Developers Are Being Interviewed](http://programmers.stackexchange.com/questions/58145/how-scala-developers-are-being-interviewed)
|
||||
* [Scala Interview Questions/Answers including Language Questions, Functional Programming Questions, Reactive Programming Questions](https://github.com/peterarsentev/Scala-Interview-Questions-Answers)
|
||||
* [Top 25 Scala Interview Questions & Answers from Toptal](http://career.guru99.com/top-25-interview-questions-on-scala/)
|
||||
|
||||
### SharePoint
|
||||
@ -558,7 +557,6 @@ Please read the [contribution guidelines](contributing.md) or [creating a list g
|
||||
* [10 Useful Random Linux Interview Questions and Answers](http://www.tecmint.com/useful-random-linux-interview-questions-and-answers/)
|
||||
* [11 Basic Linux Interview Questions and Answers](http://www.tecmint.com/basic-linux-interview-questions-and-answers/)
|
||||
* [11 Essential Linux Interview Questions from Toptal](http://www.toptal.com/linux/interview-questions)
|
||||
* [Some basic Linux questions from ComputerNetworkingNotes.com](http://computernetworkingnotes.com/rhce-interview-questions/linux-interview-questions-answers.html)
|
||||
* [Top 30 Linux System Admin Interview Questions & Answers](http://www.linuxtechi.com/experience-linux-admin-interview-questions/)
|
||||
* [Top 50 Linux Interview Questions from Career Guru](http://career.guru99.com/top-50-linux-interview-questions/)
|
||||
* [278 Test Questions and Answers for \*nix System Administrators](https://github.com/trimstray/test-your-sysadmin-skills)
|
||||
@ -581,7 +579,6 @@ Please read the [contribution guidelines](contributing.md) or [creating a list g
|
||||
* [A great list of Java interview questions](http://java2novice.com/java-interview-programs/)
|
||||
* [Algorithms playground for common interview questions written in Ruby](https://github.com/sagivo/algorithms)
|
||||
* [EKAlgorithms contains some well known CS algorithms & data structures](https://github.com/EvgenyKarkan/EKAlgorithms)
|
||||
* [Five programming problems every Software Engineer should be able to solve in less than 1 hour](http://www.shiftedup.com/2015/05/07/five-programming-problems-every-software-engineer-should-be-able-to-solve-in-less-than-1-hour)
|
||||
* [Top 10 Algorithms for Coding Interview](http://www.programcreek.com/2012/11/top-10-algorithms-for-coding-interview/)
|
||||
* [Top 15 Data Structures and Algorithm Interview Questions for Java programmer](http://javarevisited.blogspot.com.by/2013/03/top-15-data-structures-algorithm-interview-questions-answers-java-programming.html)
|
||||
* [Top Algorithms Questions by Topics](https://github.com/yangshun/tech-interview-handbook/blob/master/algorithms/README.md)
|
||||
|
||||
@ -35,14 +35,8 @@ If you have something awesome to contribute to an awesome list, this is how you
|
||||
You'll need a [GitHub account](https://github.com/join)!
|
||||
|
||||
1. Access the awesome lists GitHub page. For example: https://github.com/MaximAbramchuck/awesome-interviews
|
||||
2. Click on the `README.md` file: 
|
||||
3. Now click on the edit icon. 
|
||||
4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). 
|
||||
5. Say why you're proposing the changes, and then click on "Propose file change". 
|
||||
6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)!
|
||||
|
||||
## Updating your Pull Request
|
||||
|
||||
Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines.
|
||||
|
||||
[Here](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that.
|
||||
2. Click on the `README.md` file
|
||||
3. Now click on the edit icon
|
||||
4. Edit contents of the file using the in-browser editor to add your changes
|
||||
5. Explain why you're proposing your changes, then click "Propose file change".
|
||||
6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user