Skip to content

Commit f64043c

Browse files
committed
Swap narrative explanation and diagram with steps to set up an environment
1 parent 273eb0e commit f64043c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/contributing/first-time.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,10 +133,6 @@ After you have satisfied the above steps and have clear direction on how to proc
133133

134134
### Set up your environment
135135

136-
1. Start by [forking the project's repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your account through the GitHub interface.
137-
1. [Clone your forked repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo#cloning-your-forked-repository).
138-
1. [Configure git to sync your fork with the upstream repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo#configuring-git-to-sync-your-fork-with-the-upstream-repository).
139-
140136
As a member of the Plone Contributors Team, you do not have write access to push commits to GitHub repositories under the Plone organization.
141137
You can push commits to your fork.
142138
Thus a typical workflow will be circular in nature.
@@ -151,6 +147,10 @@ You will pull code from the upstream Plone repository, push your work from your
151147
_Plone git workflow_
152148
````
153149

150+
1. Start by [forking the project's repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your account through the GitHub interface.
151+
1. [Clone your forked repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo#cloning-your-forked-repository).
152+
1. [Configure git to sync your fork with the upstream repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo#configuring-git-to-sync-your-fork-with-the-upstream-repository).
153+
154154

155155
(write-code-label)=
156156

0 commit comments

Comments
 (0)