Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove not existing anymore link #49

Merged
merged 1 commit into from
Oct 5, 2023
Merged

Remove not existing anymore link #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,6 @@ Every repository on [GitHub.com](https://github.com/) comes equipped with a sect
Wiki should be detail, up to date and well structured. It should be easy to find required information and navigate through the pages. Use rich possibilities of Markdown in Wiki formatting. Wiki doesn't fully repeat information which is already presented at README. The following list of examples represents mentioned good practices:
- [Netflix/Hystrix](https://github.com/Netflix/Hystrix/wiki)
- [aws/aws-parallelcluster](https://github.com/aws/aws-parallelcluster/wiki)
- [mbostock/d3](https://github.com/d3/d3/wiki)
- [facebook/hhvm](https://github.com/facebook/hhvm/wiki)
- [thinkaurelius/titan](https://github.com/thinkaurelius/titan/wiki)
- [guard/guard](https://github.com/guard/guard/wiki/Guard-2.10.3-exits-when-Guardfile-is-changed)
Expand Down