Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Commits
96448ce4
Commit
96448ce4
authored
3 years ago
by
Jan Frenzel
Browse files
Options
Downloads
Patches
Plain Diff
Apply 5 suggestion(s) to 1 file(s)
parent
26391611
No related branches found
No related tags found
2 merge requests
!412
Manual attempt to merge preview into main
,
!393
Added contrib guide for browser users
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/contrib/contribute_browser.md
+5
-7
5 additions, 7 deletions
doc.zih.tu-dresden.de/docs/contrib/contribute_browser.md
with
5 additions
and
7 deletions
doc.zih.tu-dresden.de/docs/contrib/contribute_browser.md
+
5
−
7
View file @
96448ce4
...
@@ -7,17 +7,15 @@ browser only.
...
@@ -7,17 +7,15 @@ browser only.
## Preparation
## Preparation
First of all you need an account on
First of all, you need an account on
[
gitlab.hrz.tu-chemnitz.de
](
https://gitlab.hrz.tu-chemnitz.de
)
.
[
gitlab.hrz.tu-chemnitz.de
](
https://gitlab.hrz.tu-chemnitz.de
)
.
Secondly, you need access to the project
Secondly, you need access to the project
[
ZIH/hpcsupport/hpc-compendium
](
https://gitlab.hrz.tu-chemnitz.de/zih/hpcsupport/hpc-compendium
)
[
ZIH/hpcsupport/hpc-compendium
](
https://gitlab.hrz.tu-chemnitz.de/zih/hpcsupport/hpc-compendium
)
.
(ID: 8840).
The project is publicly visible, i.e., it is open to the world and any signed-in user has the
The project is publicly visible, i.e., it is open to the world and any signed-in user has the
[
Guest role
](
https://gitlab.hrz.tu-chemnitz.de/help/user/permissions.md
)
on this repository. Guests
[
Guest role
](
https://gitlab.hrz.tu-chemnitz.de/help/user/permissions.md
)
on this repository. Guests
have only very
have only very
[
limited permissions
](
https://gitlab.hrz.tu-chemnitz.de/help/user/permissions.md#project-members-permissions
)
.
[
limited permissions
](
https://gitlab.hrz.tu-chemnitz.de/help/user/permissions.md#project-members-permissions
)
.
In particular, as guest you can contribute to the documentation by
In particular, as guest
,
you can contribute to the documentation by
[
creating issues
](
howto_contribute.md#contribute-via-issue
)
, but you cannot edit files and create
[
creating issues
](
howto_contribute.md#contribute-via-issue
)
, but you cannot edit files and create
new branches.
new branches.
...
@@ -80,7 +78,7 @@ Finally, the new article needs to be added to the navigation section of the conf
...
@@ -80,7 +78,7 @@ Finally, the new article needs to be added to the navigation section of the conf
## Submitting Articles for Publication
## Submitting Articles for Publication
Once you are satisfied with your edits you are ready for publication.
Once you are satisfied with your edits
,
you are ready for publication.
Therefore, your edits need to undergo an internal review process and pass the CI/CD pipeline tests.
Therefore, your edits need to undergo an internal review process and pass the CI/CD pipeline tests.
This process is triggered by creating a "merge request", which serves the purpose of merging your edits
This process is triggered by creating a "merge request", which serves the purpose of merging your edits
into the
`preview`
branch of the repository.
into the
`preview`
branch of the repository.
...
@@ -103,5 +101,5 @@ You can follow this process under
...
@@ -103,5 +101,5 @@ You can follow this process under
(where you initiated your merge request).
(where you initiated your merge request).
If you are asked to make corrections or changes, follow the directions as indicated.
If you are asked to make corrections or changes, follow the directions as indicated.
Once your merge request has been accepted, the merge request will be closed and the branch will be deleted.
Once your merge request has been accepted, the merge request will be closed and the branch will be deleted.
At this point there is nothing else to do for you.
At this point
,
there is nothing else to do for you.
Except probably for waiting a little while until your changes become visible on the official web site.
Except probably for waiting a little while until your changes become visible on the official web site.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment