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/PULL_REQUEST_TEMPLATE.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,15 @@
1
1
<!-- Comment:
2
2
A great PR typically begins with the line below.
3
-
Replace XXXXX with the numeric part of the issue ID you created in Jira.
4
-
Note that if you want your changes backported into LTS, you need to create a Jira issue. See https://www.jenkins.io/download/lts/#backporting-process for more information.
3
+
Replace <issue-number> with the issue number.
5
4
-->
6
5
7
-
See [JENKINS-XXXXX](https://issues.jenkins.io/browse/JENKINS-XXXXX).
6
+
Fixes #<issue-number>
8
7
9
8
<!-- Comment:
10
-
If the issue is not fully described in Jira, add more information here (justification, pull request links, etc.).
9
+
If the issue is not fully described in the issue tracker, add more information here (justification, pull request links, etc.).
11
10
12
-
* We do not require Jira issues for minor improvements.
13
-
* Bug fixes should have a Jira issue to facilitate the backporting process.
14
-
* Major new features should have a Jira issue.
11
+
* We do not require an issue for minor improvements.
12
+
* Major new features should have an issue created.
15
13
-->
16
14
17
15
### Testing done
@@ -34,8 +32,8 @@ For refactoring and code cleanup changes, exercise the code before and after the
34
32
The changelog entry should be in the imperative mood; e.g., write "do this"/"return that" rather than "does this"/"returns that".
35
33
For examples, see: https://www.jenkins.io/changelog/
36
34
37
-
Do not include the Jira issue in the changelog entry.
38
-
Include the Jira issue in the description of the pull request so that the changelog generator can find it and include it in the generated changelog.
35
+
Do not include the issue in the changelog entry.
36
+
Include the issue in the description of the pull request so that the changelog generator can find it and include it in the generated changelog.
39
37
40
38
You may add multiple changelog entries if applicable by adding a new entry to the list, e.g.
41
39
- First changelog entry
@@ -82,7 +80,7 @@ The changelog generator relies on the presence of the upgrade guidelines section
82
80
83
81
### Submitter checklist
84
82
85
-
-[ ] The Jira issue, if it exists, is well-described.
83
+
-[ ] The issue, if it exists, is well-described.
86
84
-[ ] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.
87
85
-[ ] There is automated testing or an explanation as to why this change has no tests.
88
86
-[ ] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.
@@ -108,4 +106,4 @@ Before the changes are marked as `ready-for-merge`:
108
106
-[ ] Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.
109
107
-[ ] Proper changelog labels are set so that the changelog can be generated automatically.
110
108
-[ ] If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).
111
-
-[ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).
109
+
-[ ] If it would make sense to backport the change to LTS, be a _Bug_ or _Improvement_, and either the issue or pull request must be labeled as `lts-candidate` to be considered.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,8 @@ This page provides information about contributing code to the Jenkins core codeb
18
18
19
19
If you want to contribute to Jenkins, or just learn about the project,
20
20
you can start by fixing some easier issues.
21
-
In the Jenkins issue tracker we mark such issues as `newbie-friendly`.
22
-
You can find them by using this query (check the link) for [newbie friendly issues](<https://issues.jenkins.io/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20core%20AND%20labels%20in%20(newbie-friendly)>).
21
+
In the Jenkins issue tracker we mark such issues as `good first issue`.
22
+
You can find them by using this query (check the link) for [good first issues](https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20issue%22).
-[Beginners Guide To Contributing](https://www.jenkins.io/participate/)
264
-
-[List of newbie-friendly issues in the core](<https://issues.jenkins.io/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20core%20AND%20labels%20in%20(newbie-friendly)>)
264
+
-[List of good first issues in core](https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20issue%22)
0 commit comments