Skip to content

Commit

Permalink
change folder structuree
Browse files Browse the repository at this point in the history
  • Loading branch information
seabbs committed Jul 1, 2024
1 parent 1063808 commit 49add6e
Show file tree
Hide file tree
Showing 19 changed files with 7 additions and 7 deletions.
4 changes: 2 additions & 2 deletions EpiAware/docs/pages.jl
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ pages = [
]
],
"Developers" => [
"Contributing" => "man/contributing.md",
"Release checklist" => "checklist.md"
"Contributing" => "developer/contributing.md",
"Release checklist" => "developer/checklist.md"
],
"release-notes.md"
]
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,11 @@ Feel free to nominate commits that should be backported by opening an issue. Req

### `release-*` branches

* Each new minor version `x.y.0` gets a branch called `release-x.y` (a [protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)).
* New versions are usually tagged only from the `release-x.y` branches.
* For patch releases, changes get backported to the `release-x.y` branch via a single PR with the standard name "Backports for x.y.z" and label ["Type: Backport"](https://github.com/JuliaDocs/Documenter.jl/pulls?q=label%3A%22Type%3A+Backport%22). The PR message links to all the PRs that are providing commits to the backport. The PR gets merged as a merge commit (i.e. not squashed).
* The old `release-*` branches may be removed once they have outlived their usefulness.
* Patch version [milestones](https://github.com/CDCgov/Rt-without-renewal/milestones) are used to keep track of which PRs get backported etc.
* Each new minor version `x.y.0` gets a branch called `release-x.y` (a [protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)).
* New versions are usually tagged only from the `release-x.y` branches.
* For patch releases, changes get backported to the `release-x.y` branch via a single PR with the standard name "Backports for x.y.z" and label ["Type: Backport"](https://github.com/JuliaDocs/Documenter.jl/pulls?q=label%3A%22Type%3A+Backport%22). The PR message links to all the PRs that are providing commits to the backport. The PR gets merged as a merge commit (i.e. not squashed).
* The old `release-*` branches may be removed once they have outlived their usefulness.
* Patch version [milestones](https://github.com/CDCgov/Rt-without-renewal/milestones) are used to keep track of which PRs get backported etc.

## Style Guide

Expand Down
File renamed without changes.
File renamed without changes.

0 comments on commit 49add6e

Please sign in to comment.