Skip to content

Commit

Permalink
Remove mention of next-release branch
Browse files Browse the repository at this point in the history
from pull request template

`next-release` only existed while there were lots of changes still
happening to wiki as everything was new. Now that the dust has settled,
the preferred approach is to just hold of merging the change until the
release has been made.

Given our faster release cycle and fewer wiki changes this usually
doesn't inccur any issues with merge conflicts caused by other changes
to wiki being merged.
  • Loading branch information
GeckoEidechse committed Nov 15, 2023
1 parent 26b9363 commit f43d5bb
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
<!--
BEFORE OPENING A PULL REQUEST:
-> Check which version of Northstar your change targets. Documentation about feature not yet released should be merged into the `next-release` branch instead
-> If you're adding multiple independent changes (e.g. adding a section about modding while also fixing a typo on another page) it's generally recommended to split these changes into separate pull requests.
Note that pull requests containing lots of unhelpful commit messages will generally be squashed to keep commit history clean.
Expand Down

0 comments on commit f43d5bb

Please sign in to comment.