summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md (follow)
Commit message (Expand)AuthorAgeFilesLines
...
* CONTRIBUTING.md: Minor fixesSilvan Mosberger2023-08-141-31/+33
* CONTRIBUTING.md: New section on which branch to useSilvan Mosberger2023-08-141-31/+50
* CONTRIBUTING.md: Move rebasing section up•••Right into the "How to propose a change" section, because that's where it's relevant Silvan Mosberger2023-08-131-74/+74
* CONTRIBUTING.md: Remove duplicated section•••How to force push to PR's is already explained in the "How to propose a change" section at the beginning Silvan Mosberger2023-08-131-7/+0
* CONTRIBUTING.md: Minor formatting fixesSilvan Mosberger2023-08-131-27/+24
* CONTRIBUTING.md: Clean up releases sectionSilvan Mosberger2023-08-131-51/+43
* CONTRIBUTING.md: Move release sections together•••Will be cleaned up in the next commit Silvan Mosberger2023-08-131-71/+71
* CONTRIBUTING.md: Clean up and condense staging workflow sectionSilvan Mosberger2023-08-131-61/+46
* CONTRIBUTING.md: Replace staging workflow diagram•••Can't be rendered in GitHub markdown, replacing it with a Git branch diagram using mermaid Silvan Mosberger2023-08-131-20/+42
* CONTRIBUTING.md: Move flow of changes section upSilvan Mosberger2023-08-131-145/+145
* CONTRIBUTING.md: Clean up "Making patches" section•••Moving and collecting bits into the appropriate places, also writing some new sentences Silvan Mosberger2023-08-131-28/+23
* CONTRIBUTING.md: Write a new section on how to propose a change•••Removing paragraphs from the other sections that aren't necessary anymore Silvan Mosberger2023-08-131-19/+60
* CONTRIBUTING.md: Coding conventions -> code conventions•••It's not conventions about how to do coding, it's about what the code should look like Silvan Mosberger2023-08-131-1/+2
* CONTRIBUTING.md: Collect paragraphs into a new commit conventions sectionSilvan Mosberger2023-08-131-49/+41
* CONTRIBUTING.md: Move pull request template section to the bottomSilvan Mosberger2023-08-131-70/+69
* CONTRIBUTING.md: Add overviewSilvan Mosberger2023-08-131-0/+9
* CONTRIBUTING.md: Add introSilvan Mosberger2023-08-131-0/+7
* Move CONTRIBUTING-new.md to CONTRIBUTING.md•••The -new version was assembled in the previous commits Silvan Mosberger2023-08-131-0/+682
* CONTRIBUTING.md: Remove temporarily•••So that the CONTRIBUTING-new.md can take its place and Git detect the rename Silvan Mosberger2023-08-131-11/+0
* CONTRIBUTING.md: Move opening issues section to Nixpkgs manual•••This isn't relevant to contributors specifically, it applies to all users Silvan Mosberger2023-08-131-6/+0
* CONTRIBUTING.md: Rough move to new contribution doc files•••No content was changed, new titles are wrapped with () to signal that they will need to be decided on in a future commit. Silvan Mosberger2023-08-131-159/+0
* CONTRIBUTING.md: highlight the need for setting `meta.mainProgram`Anderson Torres2023-08-121-2/+3
* contributing: Explain how to run common tests•••As a beginning contributor, it is far from obvious where to find tests, how to run individual tests locally for quick development, and which tests do what. The new "Testing changes" section aims to help with all of these. Co-authored-by: Emily <git@emilylange.de> Victor Engmark2023-06-201-0/+9
* Merge pull request #238126 from nikstur/contributing-release-notes•••CONTRIBUTING.md: remove historical triviaPol Dellaiera2023-06-171-13/+0
|\
| * CONTRIBUTING.md: remove historical trivia•••The transition to markdown is done now and the historical trivia is not helpful for first time contributers who are the primary audience for this document. Telling the user to edit a file by editing a file is superfluous. nikstur2023-06-161-13/+0
* | CONTRIBUTING.md: Add section for mass-ping handlingpiegames2023-06-121-2/+35
|/
* Release NixOS 23.05Raito Bezarius2023-05-311-8/+8
* CONTRIBUTING.md: Clarify guidelines for `meta.description`Jean-Paul Calderone2023-04-241-0/+1
* nixos/manual: remove md-to-db•••with manual chapters no longer needing pandoc for their conversion to xml we can get rid of this source of confusion, and its huge cache of xml files. pennae2023-02-101-3/+6
* CONTRIBUTING.md: clarify some directives about `meta` attributesAndersonTorres2022-12-311-1/+4
* CONTRIBUTING: add links to online resourcesSandro Jäckel2022-12-241-1/+1
* treewide: fix typosfigsoda2022-12-171-1/+1
* CONTRIBUTING: loose squash merging rules (#204988)•••Co-authored-by: Naïm Favier <n@monade.li>Sandro2022-12-141-3/+3
* Merge pull request #196153 from ncfavier/contributing-no-squashNaïm Favier2022-12-021-0/+4
|\
| * CONTRIBUTING.md: "no squash merges"Naïm Favier2022-10-151-0/+4
* | Release NixOS 22.11Martin Weinelt2022-11-301-8/+8
* | CONTRIBUTING: Reference release notes in package bumps•••This change improves the recommendation for good commit messages to include release notes on package bumps. Including the release notes increases the likelihood that they will be taken into consideration during review. Having them included in the review is important to be able to judge whether changes made during a version bump are sensible, sufficient or complete. The burden of retrieving the release notes for arbitrary package bumps should not rest on the relatively small group of reviewers. Signed-off-by: Martin Weinelt <hexa@darmstadt.ccc.de> origin/contributing-pkg-bump-rls-notesMartin Weinelt2022-11-141-1/+1
|/
* Merge #175352: CONTRIBUTING.md: simplify rebasing instructionspiegames2022-08-151-13/+14
|\
| * CONTRIBUTING.md: simplify rebasing instructions•••Makes the instructions easier to remember (and type) using the `git rebase --onto A...B` syntax to find the merge base between A and B (which has been in git for at least 10 years). We also assume that the merge base between staging and master is also the merge base between staging and the current branch (since it is based on master), and giving master as the <upstream> branch makes git consider the commits in the current branch that are not in master, so there's no need to compute the merge base between master and the current branch. In the same spirit of discouraging copy-and-paste, use a placeholder name for the current branch instead of `$(git branch --show-current)`. Naïm Favier2022-05-291-13/+14
* | CONTRIBUTING.md: use 22.05 as target branch for backportsMarkus S. Wamser2022-05-311-2/+2
* | Release 22.05Janne Heß2022-05-301-7/+5
|/
* CONTRIBUTING.md: document using labels for backportingArnout Engelen2022-05-281-0/+6
* CONTRIBUTING.md: encourage linking release notes on updates•••Makes it easier for reviewers to look through the changes and is a sane default to reference if one exists. Martin Weinelt2022-04-051-1/+2
* fixup! CONTRIBUTING: rebase master to staging without pinging peopleMartin Weinelt2022-04-031-2/+13
* CONTRIBUTING: rebase master to staging without pinging people•••Co-Authored-By: Martin Weinelt <hexa@darmstadt.ccc.de> Co-Authored-By: Janne Heß <janne@hess.ooo> Jörg Thalheim2022-03-301-0/+29
* CONTRIBUTING: Make clearer where branch policy can be foundNiklas Hambüchen2022-01-041-1/+5
* .github/PULL_REQUEST_TEMPLATE.md, CONTRIBUTING.md: 21.11 -> 22.05 (#147977)•••* .github/PULL_REQUEST_TEMPLATE.md: 21.11 -> 22.05 * CONTRIBUTING.md: 21.11 -> 22.05Bobby Rong2021-11-301-8/+8
* CONTRIBUTING.md: fix link to COPYING•••The current link 404s when viewed on GitHub due to using a relative path that refers to an upper directory.Smittyvb2021-08-101-1/+1
* CONTRIBUTING.md: Move to repo root, where it is more visible.•••We found that many users found it difficult to locate this document. Github supports it in the root, see: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors Niklas Hambüchen2021-06-261-0/+85
* Move CONTRIBUTING.md to .github•••See https://github.com/blog/2111-issue-and-pull-request-templates. Eelco Dolstra2016-02-191-15/+0