-
Notifications
You must be signed in to change notification settings - Fork 558
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.
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
Improve contributing docs #9732
base: master
Are you sure you want to change the base?
Improve contributing docs #9732
Conversation
README.md
Outdated
To contribute a new recipe, you can either | ||
For detailed information about contributing, go to ["CONTRIBUTING.md"](https://github.com/JuliaPackaging/Yggdrasil/blob/master/CONTRIBUTING.md). For a quick overview, continue reading. | ||
|
||
To update the version to build for an existing recipe, simply open a PR to this repository making the required tweaks. This usually boils down to only updating the version number and the source (e.g., URL and hash for an archive, or the revision for a git repository) of the relevant `build_tarballs.jl` file, but in some cases more changes may be needed. For an example, see [this PR](https://github.com/JuliaPackaging/Yggdrasil/pull/8833). The version number should be easy to find, and the URL + hash can be found by clicking the release, clicking the final commit in the release, and copying the information from the URL bar. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instructions to find the commit hash are specific to github though, which isn't the only web hosting service in the world.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, but it is all I know. This should cover many (most?) cases and is therefore useful as-is, and more examples are ofc very welcome.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still, this sounds as if it's a generic recommendation, which is not.
Co-authored-by: Max Horn <[email protected]>
This PR adds a link to the CONTRIBUTING file in the readme.
It also moves the information on updating an existing release to the top. This is because it was really easy to do, and putting the easy stuff first help ensuring that people who want to do the easy stuff do not stop/quit at the hard stuff.
This PR also and removes the separate section for it, as the slightly smaller heading in markdown is usually not sufficient to signal that it is a subsection. Also, there is just a single paragraph of instructions, so a new heading was overkill.