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: README.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ To contribute to the LF Energy Archimate models you need [Archi](https://www.arc
22
22
23
23
2. In Archi, select "Manage Plug-ins..." from the main Help menu. From the Plug-ins Manager window, select "Install New..." and select the **coArchi** plug-in zip file. You may need to restart Archi to activate the plug-in. Please ensure the plug-in version supports the installed version of Archi.
3. If your plug-in installation was successful, the [**Collaboration**] menu item should be visible appear on the application menu in Archi after restarting Archi.
30
30
@@ -45,7 +45,7 @@ Alternatively, you can follow the steps below:
45
45
46
46
2. Select [**Developer settings**] from the menu on the left-hand of the page
3. Select [**Personal access tokens**] and then [**Tokens (classic)**]
51
51
4. Select [**Generate new token**] and then [**Generate new token (classic)**]
@@ -65,7 +65,7 @@ Once you have configured Archi and coArchi, and generated your Github Personal A
65
65
66
66
1. In Archi, select [**Import Remote Model to Workspace**] from **Collaboration** menu. You may need to provide Archi a master password to unlock this feature. **IMPORTANT**: YOU CANNOT RETRIEVE THE MASTER PASSWORD AFTERWARDS. IF YOU LOOSE IT YOU MAY WILL NEED TO REINSTALL ARCHI.
1. In Archi, select [**Toggle Collaboration Workspace**] and [**Toggle Branches View**] from the **Collaboration** menu. The Workspace and Branch windows will be docked within Archi. Archi/coArchi supports repository branches.
The Collaboration Workspace is used to navigate between different models and individual branches checked out while the Branches View provide the ability to manipulate branches within the selected model.
91
91
@@ -95,11 +95,11 @@ The Collaboration Workspace is used to navigate between different models and ind
95
95
96
96
1. To refresh your local copy of the model, open the model / branch from the Collaboration Workspace and select [**Refresh Model**] from the **Collaboration** application menu.
3. Select [**Add branch and checkout**]. This will create the local topic branch and set it as the active branch. This action won't create the upstream branch (on [Github server](https://github.com/NBility-Model) yet).
4. The final step is to publish the new topic branch. This will make the new topic branch available on [GitHub.co](https://github.com/NBility-Model). To publish your new topic branch, select [**Publish changes**] from the **Collaboration** menu.
5. To ensure that your new topic branch have been successfully published, you can verify by visiting your topic branch on https://github.com/NBility-Model to see if your new topic branch appears in the specific repository you've worked on.
127
127
@@ -131,22 +131,22 @@ To protect the integrity of the main branch and avoid overwriting updates from s
131
131
1. In Archi, select [**Toggle Branches View**] from the **Collaboration** menu.
132
132
2. In archi, right click on the branch you like to switch to and click on [**Switch branch**].
2. Enter your user details and a commit message. By committing changes you create a local snapshot of the repository into a single package. **IMPORTANT: This does not upload the changes to the upstream branch, but only create a local packaged copy**.
3. The final step is to publish the committed package back to the upstream repository. This will insert the last committed package into the upstream branchat GitHub.com. To publish your latest changes, select [**Publish changes**] from the **Collaboration** menu.
4. To ensure that your changes have been successfully committed and published, you can verify by visiting https://github.com/NBility-Model to see if your commit appears in the specific branch you've worked on.
152
152
@@ -157,17 +157,17 @@ On regular intervals all committed and published branches need to be merged into
157
157
1. Log onto your GitHub Account at [GitHub.com](github.com)
158
158
2. In https://github.com/NBility-Model, create a Github pull request from your topic branch on by clicking on the button [**Compare & Pull Request**].
4. Pull requests will be reviewed by one of the maintainers of NBility Model who may discuss, offer constructive feedback, request changes, or approve the work.
167
167
168
168
5. Upon receiving the sign-off of one of the maintainers of NBility Model you may merge your changes, or if you do not have permission to do that, you may request a maintainer to merge it for you.
0 commit comments