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: doc/source/devel/core_developer.rst
+1-8Lines changed: 1 addition & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,9 @@ Core Developer Guide
4
4
====================
5
5
6
6
As a core developer, you should continue making pull requests
7
-
in accordance with the :ref:`contributor_guide`.
7
+
in accordance with the :ref:`devguide`.
8
8
You are responsible for shepherding other contributors through the review process.
9
-
You should be familiar with our :ref:`mission_and_values`.
10
9
You also have the ability to merge or approve other contributors' pull requests.
11
-
Much like nuclear launch keys, it is a shared power: you must merge *only after*
12
-
another core developer has approved the pull request, *and* after you yourself have carefully
13
-
reviewed it. (See `Reviewing`_ and especially `Merge Only Changes You
14
-
Understand`_ below.) To ensure a clean git history, use GitHub's
15
-
`Squash and Merge <https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github>`__
16
-
feature to merge, unless you have a good reason not to do so.
0 commit comments