summary refs log tree commit diff
path: root/CONTRIBUTING.md
AgeCommit message (Collapse)AuthorFilesLines
2023-09-06CONTRIBUTING.md: Reword changes acceptable for backportSilvan Mosberger1-9/+9
It wasn't entirely clear if the list was acceptable or not from the wording.
2023-09-04CONTRIBUTING: Add note about how to commit new maintainers-list.nix entryMatthias Beyer1-0/+5
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
2023-08-28docs: fix link to Nix manual on sandbox configHraban Luyat1-1/+1
2023-08-20CONTRIBUTING: remove suggestion about the order of argumentsAnderson Torres1-2/+0
Particularities about style should be enforced at the tooling level (linters, code beautifiers etc.). Otherwise, it adds more weight on the PR reviewing, distracting both authors and reviewers from the substance of the changes.
2023-08-14CONTRIBUTING.md: Move boot loader-specific sentence to pkgs/README.mdSilvan Mosberger1-2/+0
This needs a rewrite at some point..
2023-08-14CONTRIBUTING.md: Typos and formattingSilvan Mosberger1-9/+9
- Fix sentence about meeting contributing standards - pkgs -> packages - Use emoji's because GitHub renders the :*: things weird sometimes - Move a dot Co-authored-by: Rémi NICOLE <minijackson@users.noreply.github.com>
2023-08-14CONTRIBUTING.md: Minor content updates based on reviewsSilvan Mosberger1-3/+8
- Contributing without a GitHub account - Mention OfBorg - nix.useSandbox -> nix.settings.sandbox - nixpkgs-review is good for not just version updates Co-authored-by: Rémi NICOLE <minijackson@users.noreply.github.com>
2023-08-14CONTRIBUTING.md: Move sections aroundSilvan Mosberger1-209/+223
Yeah I'm totally getting lazy with the commits, but it's really hard and takes a long time..
2023-08-14CONTRIBUTING.md: Minor fixesSilvan Mosberger1-33/+35
2023-08-14CONTRIBUTING.md: New section on which branch to useSilvan Mosberger1-31/+50
2023-08-13CONTRIBUTING.md: Move rebasing section upSilvan Mosberger1-74/+74
Right into the "How to propose a change" section, because that's where it's relevant
2023-08-13CONTRIBUTING.md: Remove duplicated sectionSilvan Mosberger1-7/+0
How to force push to PR's is already explained in the "How to propose a change" section at the beginning
2023-08-13CONTRIBUTING.md: Minor formatting fixesSilvan Mosberger1-27/+24
2023-08-13CONTRIBUTING.md: Clean up releases sectionSilvan Mosberger1-51/+43
2023-08-13CONTRIBUTING.md: Move release sections togetherSilvan Mosberger1-71/+71
Will be cleaned up in the next commit
2023-08-13CONTRIBUTING.md: Clean up and condense staging workflow sectionSilvan Mosberger1-65/+50
2023-08-13CONTRIBUTING.md: Replace staging workflow diagramSilvan Mosberger1-24/+46
Can't be rendered in GitHub markdown, replacing it with a Git branch diagram using mermaid
2023-08-13CONTRIBUTING.md: Move flow of changes section upSilvan Mosberger1-145/+145
2023-08-13CONTRIBUTING.md: Clean up "Making patches" sectionSilvan Mosberger1-28/+23
Moving and collecting bits into the appropriate places, also writing some new sentences
2023-08-13CONTRIBUTING.md: Write a new section on how to propose a changeSilvan Mosberger1-25/+66
Removing paragraphs from the other sections that aren't necessary anymore
2023-08-13CONTRIBUTING.md: Coding conventions -> code conventionsSilvan Mosberger1-1/+2
It's not conventions about how to do coding, it's about what the code should look like
2023-08-13CONTRIBUTING.md: Collect paragraphs into a new commit conventions sectionSilvan Mosberger1-49/+41
2023-08-13CONTRIBUTING.md: Move pull request template section to the bottomSilvan Mosberger1-70/+69
2023-08-13CONTRIBUTING.md: Add overviewSilvan Mosberger1-0/+9
2023-08-13CONTRIBUTING.md: Add introSilvan Mosberger1-0/+7
2023-08-13Move CONTRIBUTING-new.md to CONTRIBUTING.mdSilvan Mosberger1-0/+682
The -new version was assembled in the previous commits
2023-08-13CONTRIBUTING.md: Remove temporarilySilvan Mosberger1-11/+0
So that the CONTRIBUTING-new.md can take its place and Git detect the rename
2023-08-13CONTRIBUTING.md: Move opening issues section to Nixpkgs manualSilvan Mosberger1-6/+0
This isn't relevant to contributors specifically, it applies to all users
2023-08-13CONTRIBUTING.md: Rough move to new contribution doc filesSilvan Mosberger1-159/+0
No content was changed, new titles are wrapped with () to signal that they will need to be decided on in a future commit.
2023-08-12CONTRIBUTING.md: highlight the need for setting `meta.mainProgram`Anderson Torres1-2/+3
2023-06-20contributing: Explain how to run common testsVictor Engmark1-0/+9
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>
2023-06-17Merge pull request #238126 from nikstur/contributing-release-notesPol Dellaiera1-13/+0
CONTRIBUTING.md: remove historical trivia
2023-06-16CONTRIBUTING.md: remove historical trivianikstur1-13/+0
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.
2023-06-12CONTRIBUTING.md: Add section for mass-ping handlingpiegames1-2/+35
2023-05-31Release NixOS 23.05Raito Bezarius1-8/+8
2023-04-24CONTRIBUTING.md: Clarify guidelines for `meta.description`Jean-Paul Calderone1-0/+1
2023-02-10nixos/manual: remove md-to-dbpennae1-3/+6
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.
2022-12-31CONTRIBUTING.md: clarify some directives about `meta` attributesAndersonTorres1-1/+4
2022-12-24CONTRIBUTING: add links to online resourcesSandro Jäckel1-1/+1
2022-12-17treewide: fix typosfigsoda1-1/+1
2022-12-14CONTRIBUTING: loose squash merging rules (#204988)Sandro1-3/+3
Co-authored-by: Naïm Favier <n@monade.li>
2022-12-02Merge pull request #196153 from ncfavier/contributing-no-squashNaïm Favier1-0/+4
2022-11-30Release NixOS 22.11Martin Weinelt1-8/+8
2022-11-14CONTRIBUTING: Reference release notes in package bumpsMartin Weinelt1-1/+1
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>
2022-10-15CONTRIBUTING.md: "no squash merges"Naïm Favier1-0/+4
2022-08-15Merge #175352: CONTRIBUTING.md: simplify rebasing instructionspiegames1-13/+14
2022-05-31CONTRIBUTING.md: use 22.05 as target branch for backportsMarkus S. Wamser1-2/+2
2022-05-30Release 22.05Janne Heß1-7/+5
2022-05-29CONTRIBUTING.md: simplify rebasing instructionsNaïm Favier1-13/+14
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)`.
2022-05-28CONTRIBUTING.md: document using labels for backportingArnout Engelen1-0/+6
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-22 08:19:53 +0000