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: docs/contributing/first-time.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,10 +133,6 @@ After you have satisfied the above steps and have clear direction on how to proc
133
133
134
134
### Set up your environment
135
135
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
-
140
136
As a member of the Plone Contributors Team, you do not have write access to push commits to GitHub repositories under the Plone organization.
141
137
You can push commits to your fork.
142
138
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
151
147
_Plone git workflow_
152
148
````
153
149
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).
0 commit comments