You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
2
2
3
-
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
3
+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md) before filling out this issue template**.
4
4
5
5
## [Please follow one of the issue templates](https://github.com/arcticicestudio/nord-docs/issues/new/choose)
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bugs.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ about: Report a bug that is caused by the code in this repository
5
5
6
6
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
7
7
8
-
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
8
+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md) before filling out this issue template**.
9
9
10
10
## Prerequisites
11
11
@@ -15,7 +15,7 @@ Please do your best to provide as much information as possible and use a clear a
15
15
16
16
-**Ensure the bug has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/nord-docs/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
17
17
-**Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
18
-
-**Ensure the bug is reproducible and has not already been fixed** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-docs/tree/develop) branch.
18
+
-**Ensure the bug is reproducible and has not already been fixed** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`master`](https://github.com/arcticicestudio/nord-docs/tree/master) branch.
19
19
20
20
## Metadata Head
21
21
@@ -43,7 +43,7 @@ What actually happens?
43
43
44
44
## Example
45
45
46
-
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md#mcve)
46
+
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md#mcve)
47
47
48
48
**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the bug.**
49
49
The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/enhancement.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ about: Submit an enhancement suggestion for new features or minor improvements t
5
5
6
6
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
7
7
8
-
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
8
+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md) before filling out this issue template**.
9
9
10
10
## Prerequisites
11
11
@@ -15,7 +15,7 @@ Please do your best to provide as much information as possible and use a clear a
15
15
16
16
-**Ensure the enhancement has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/nord-docs/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
17
17
-**Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
18
-
-**Check if the enhancement has already been implemented** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-docs/tree/develop) branch to ensure that the feature or improvement has not already been added.
18
+
-**Check if the enhancement has already been implemented** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`master`](https://github.com/arcticicestudio/nord-docs/tree/master) branch to ensure that the feature or improvement has not already been added.
19
19
20
20
## Metadata Head
21
21
@@ -41,7 +41,7 @@ If you've considered alternative features or solutions please describe it clearl
41
41
42
42
## Example
43
43
44
-
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md#mcve)
44
+
Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md#mcve)
45
45
46
46
**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the enhancement.**
47
47
The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
<!-- Click on the "Preview" tab to render the instructions in a more readable format -->
2
2
3
-
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
3
+
> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md) before filling out this issue template**.
4
4
5
5
## Prerequisites
6
6
@@ -10,8 +10,8 @@ Please do your best to provide as much information as possible and use a clear a
10
10
11
11
-**Ensure the pull request has not already been submitted by using the [GitHub Issue search](https://github.com/arcticicestudio/nord-docs/issues)** — check if this enhancement or bug fix has already been suggested. If it has **and the pull request is still open**, add your additions as comment or [suggest a change](https://help.github.com/articles/incorporating-feedback-in-your-pull-request/#applying-a-suggested-change) to the existing pull request instead of opening a new one. If you find a closed pull request that seems to be similar to this one, include a link to the original pull request in the [metadata head](#metadata-head) section of this new pull request.
12
12
-**Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
13
-
-**Ensure to adhere to the [pull request contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/develop/CONTRIBUTING.md#pull-requests)**, especially the one for tests and documentations.
14
-
-**Check if the enhancement has already been implemented or bug already fixed** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-docs/tree/develop) branch to ensure that the enhancement or bug fix has not already been added.
13
+
-**Ensure to adhere to the [pull request contribution guidelines](https://github.com/arcticicestudio/nord-docs/blob/master/CONTRIBUTING.md#pull-requests)**, especially the one for tests and documentations.
14
+
-**Check if the enhancement has already been implemented or bug already fixed** — use the [latest version](https://github.com/arcticicestudio/nord-docs/releases/latest) and [`master`](https://github.com/arcticicestudio/nord-docs/tree/master) branch to ensure that the enhancement or bug fix has not already been added.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-18
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ A bug is a _demonstrable problem_ that is caused by the code in the repository.
31
31
32
32
-**Use the [GitHub Issue search][gh-issues]** — check if the issue has already been reported. If it has **and the issue is still open**, add a comment to the existing issue instead of opening a new one. If you find a closed issue that seems like it is the same thing that you are experiencing, open a new issue and include a link to the original issue in the body of your new one.
33
33
-**Determine [which repository the contribution belongs to](#repository-assignment).**
34
-
-**Check if the issue has been fixed** — try to reproduce it using the [latest version][gh-releases-latest] and [`develop`][gh-branch-develop] branch in the repository.
34
+
-**Check if the issue has been fixed** — try to reproduce it using the [latest version][gh-releases-latest] and [`master`][gh-branch-master] branch in the repository.
35
35
-**Isolate the problem** — ideally create a [MCVE](#mcve).
36
36
37
37
When you are creating a bug report, please provide as much detail and context as possible. Fill out on of [the required templates][gh-issues-template-bug], the information it asks helps maintainers to reproduce the problem and resolve issues faster.
@@ -56,7 +56,7 @@ This section guides you through submitting an enhancement suggestion, including
56
56
57
57
-**Use the [GitHub Issues search][gh-issues]** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one.
58
58
-**Determine [which repository the contribution belongs to](#repository-assignment).**
59
-
-**Check if the enhancement has already been implemented** — use the [latest version][gh-releases-latest] and [`develop`][gh-branch-develop] branch to ensure that the feature or improvement has not already been added.
59
+
-**Check if the enhancement has already been implemented** — use the [latest version][gh-releases-latest] and [`master`][gh-branch-master] branch to ensure that the feature or improvement has not already been added.
60
60
-**Provide a reduced show case** — ideally create a [MCVE](#mcve).
61
61
62
62
Before creating enhancement suggestions, please check if your idea fits with the scope and provide as much detail and context as possible using a structured layout like the [the issue template][gh-issues-template-enhancement].
@@ -85,7 +85,7 @@ When you are submitting an pull request, please provide as much detail and conte
85
85
-**Lint and test before submitting the pull request**.
86
86
-**Make sure to create the pull request from a [topic branch][git-docs-branching-workflows]**.
87
87
88
-
**All pull requests must be send against the [`develop`][gh-branch-develop] branch** - Please read the [branch organization](#branch-organization) section below for details about the branching model.
88
+
**All pull requests must be send against the [`master`][gh-branch-master] branch** - Please read the [branch organization](#branch-organization) section below for details about the branching model.
89
89
90
90
### Documentations
91
91
@@ -95,12 +95,9 @@ You can help improve the docs and guides by making them more coherent, consisten
95
95
96
96
## Branch Organization
97
97
98
-
Nord uses the [gitflow][gitflow] branching model. The repository consists of two core branches with an infinite development lifecycle:
98
+
Nord uses the [GitHub Flow][github-flow] branching model. The repository consists of the `master`core branch with an infinite development lifecycle. The source code of [Git‘s `HEAD`][git-docs-internals-head] in this branch contains the latest development state and reflects all tagged release versions.
99
99
100
-
-`master` - The source code of `HEAD` always reflects a tagged release version.
101
-
-`develop` - The default branch where the source code of `HEAD` always reflects a state with the latest development state.
102
-
103
-
**All [pull requests](#pull-requests) for the limited development lifecycle _story_/_topic_ branches must be send against the `develop` branch**.
100
+
**All [pull requests](#pull-requests) for limited development lifecycle _story_/_topic_ branches must be send against the `master` branch**.
104
101
105
102
<!-- lint disable no-heading-punctuation -->
106
103
@@ -194,33 +191,35 @@ Every significant change is documented in the [changelog][gh-changelog].
194
191
Thanks for the inspirations and attributions to GitHub's [Open Source Guides][os-guide] and various contribution guides of large open source projects like [Atom][gh-atom-contrib], [React][react-contrib] and [Ruby on Rails][ruby-on-rails-contrib].
0 commit comments