How to make casual contributions
To make changes in Docs page hosted on GitLab, you have a built-in web editor that makes your first contribution easier than ever. Start editing documentation on GitLab Web IDE that you can launch in one click. You do not need special permissions or write access to the original project.
There is no need to install apps or clone repos on your local computer, or run Git commands in terminal.
There is no risk of breaking anything.
This guide is for GitLab-hosted repo.
How to edit document with Web IDE
Step 1. Select a page to edit
Find a Docs page you want to edit.
Navigate to the top right and locate three buttons.
Click the middle edit the page button to make corrections.
|The left button forwards to the version history of the opened Docs page as a reference. The right button report an issue is when you report any change or update required.|
Log in to your existing GitLab account
Use the SAML link to link your account to FAS
You will be redirected and asked for your FAS credentials if needed
Grant permission to Fedora
Create one if you do not have one yet (see the image below).
|This contributor guide walks through the new Web IDE, introduced in GitLab 15.7 release. The guide also reflects a latest change about how to update fork.|
Step 2. Create your project (copy)
Click the Open in Web IDE button. Alternatively, press . (dot) in keyboard to launch Web IDE.
Fork a project first time
Click the Fork button.
The Fork button appears only the first time you contribute to the repository of a given Docs page. If you are contributing to the Fedora project first time and you do not have write access for the repository you want to contribute to, you need to fork a project.
A fork is a personal copy of the repository, which you create in your namespace.
Forked a project before
If you have a forked project before, you will be forwarded automatically to the next step without the Fork button.
If you do not launch Web IDE from your fork, edit fork in Web IDE button will appear in lieu of the Open in Web IDE button. Then you will be prompted to go to fork and checkout to your fork.
Go to your forked project.
Check the status of your fork underneath Web IDE button.
If your fork shows Up to date with the upstream repository, go to step 3 in Web IDE.
If your fork is behind upstream, you will see UI text how far your fork is behind.
Click Update fork button.
The fork will display Up to date with the upstream repository
Update fork button disappears after fork is updated
Step 3. Create a new branch (version)
On your forked project, create a new branch and switch to it following the steps below.
On the status bar underneath in the lower-left corner, click the current branch name (normally main).
From the dropdown list, select Create new branch….
Type the branch name that is specific to a task.
Checkout to a new branch. Click Yes to the following pop-up box.
Are you sure you want to checkout <branch-name>? Any unsaved changes will be lost.
Step 4. Edit and save changes
Now, make the necessary changes in Web IDE. To write with consistency, refer to The docs style guide
Once you’ve finished, select the source control button and click the file underneath changes below Commit & Push button) to view your changes.
Type a commit message and click Commit & Push. Click No to commit to existing branch.
Step 5. Create Merge Request (MR)
In the lower-right corner, you will find three options - create MR, Go to project, Continue working.
Click Create MR to create merge request.
Edit the title and the description of the page.
Scroll down to the blue Create merge request button and click it.
|Go to project option is suitable when you made small commits by stage and want to squash them into one. Continue working is when you want to make smaller commits by sub tasks. If you select Create MR, the UI will navigate to merge request.|
If merge request is successful, you will see the following result in the lower-middle of merge request.
Ready to merge by members who can write to the target branch.
Step 6. Review
Your request will be reviewed by Docs team. You will expect one of the following actions.
Reviewers ask you to revise your changes
Reject and close MR within reason
Whatever the case it is, MR comments facilitate collaboration between contributors and reviewers. Everyone can learn from those comments and corrections.
Once your MR is approved, the process is complete.
Thanks for your contribution!
Want to help? Learn how to contribute to Fedora Docs ›