Skip to content
This repository was archived by the owner on Aug 31, 2021. It is now read-only.

Commit 28bf529

Browse files
author
livecodeali
committed
[[ Community Docs ]] Remove references to community-docs in favour of develop
1 parent bfadf0d commit 28bf529

10 files changed

+12
-12
lines changed

docs/contributing_to_docs.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -154,22 +154,22 @@ website, without having to download any software or use the command line.
154154

155155
### Making your dictionary change
156156

157-
**Navigate to the file you want to modify in the [dictionary folder of the community-docs branch](https://github.com/livecode/livecode/blob/community-docs/docs/dictionary).**
157+
**Navigate to the file you want to modify in the [dictionary folder of the develop branch](https://github.com/livecode/livecode/blob/develop/docs/dictionary).**
158158

159159
For example, the accept command is at:
160-
https://github.com/livecode/livecode/blob/community-docs/docs/dictionary/command/accept.lcdoc
160+
https://github.com/livecode/livecode/blob/develop/docs/dictionary/command/accept.lcdoc
161161

162162
Either go directly to the community docs branch URL
163-
(https://github.com/livecode/livecode/tree/community-docs) or if you are
164-
on the main LiveCode repository page, select 'community-docs' from the
163+
(https://github.com/livecode/livecode/tree/develop) or if you are
164+
on the main LiveCode repository page, select 'develop' from the
165165
branch dropdown menu:
166166

167167
![](images/branch-dropdown.png)
168168

169-
You should see that the community-docs branch is selected both in the
169+
You should see that the develop branch is selected both in the
170170
label of the dropdown and the url of your browser.
171171

172-
![](images/community-docs-branch.png)
172+
![](images/develop-branch.png)
173173

174174
Now use the file system browser to find the file you want to modify, and
175175
click on it.
@@ -239,7 +239,7 @@ and description
239239

240240
>*Note:* Please ensure the pull request has the correct base branch and
241241
comparison branch. The base fork should be `livecode/livecode`, with
242-
base branch `community-docs`, and the head fork should be
242+
base branch `develop`, and the head fork should be
243243
`<your user name>/livecode` with compare branch something like `patch-1`
244244
(unless you have renamed it).
245245

@@ -407,7 +407,7 @@ Click commit to <branch>
407407

408408
Then click "Submit pull request"
409409

410-
Make sure the target branch is livecode/community-docs
410+
Make sure the target branch is livecode/develop
411411

412412
Check the pull request has appeared in
413413
https://github.com/livecode/livecode/pulls
@@ -436,13 +436,13 @@ make sure your name and email address are set up
436436

437437
`git config --global user.email "<your email address>"`
438438

439-
checkout the `community-docs` branch
439+
checkout the `develop` branch
440440

441-
`git checkout community-docs`
441+
`git checkout develop`
442442

443443
ensure it is up to date
444444

445-
`git pull upstream community-docs`
445+
`git pull upstream develop`
446446

447447
create a new branch for your docs changes, for example
448448

@@ -480,7 +480,7 @@ Navigate to your fork on the Git website, `https://github.com/<your user name>/l
480480
You should see a link to the recently pushed branch, and an invitation to submit a pull request.
481481
Click this.
482482

483-
Ensure the base fork is livecode/livecode, and the base is community-docs.
483+
Ensure the base fork is livecode/livecode, and the base is develop.
484484

485485
Click create pull request.
486486

docs/images/branch-dropdown.png

38.8 KB
Loading
-89.9 KB
Binary file not shown.

docs/images/develop-branch.png

46.9 KB
Loading

docs/images/edit-file-again.png

-367 Bytes
Loading

docs/images/editing-file.png

1.33 KB
Loading
1.2 KB
Loading

docs/images/open-pull-request.png

-776 Bytes
Loading
-7.68 KB
Loading

docs/images/pull-request.png

-220 Bytes
Loading

0 commit comments

Comments
 (0)