GitHub way

This guide tells you how you can easily request and edit a page on this website. You do this using GitHub. For other ways of contributing, see How to contribute.

Prerequisite: create a GitHub account before you start. It’s easy and free.

Announce and discuss your proposal through GitHub “issues”

1. Go to the ELIXIR Training SPLASH repo on GitHub.
2. Click on “Issues” in the top menu bar and look at the existing issues. See if your idea or suggestion is already being discussed.
   • If an issue exists, add your comments. If you want to edit the content discussed, let people know through the comments.
   • If no relevant issue exists, create a new issue by clicking on the green “New issue” button on the right, and choose one of the issues templates. You can find more information on creating issues in the GitHub documentation.
3. Discuss your idea with the editors through comments in the issues. You will be notified when others comment on your issues. Read the comments and write your opinion/questions/answers in the “Leave a comment” box and click on the green “Comment” button on the right.
4. You can always return to your opened issue by going to the issues section of our GitHub repo.

Write your content and make a pull request

1. When you and the editors have agreed on what you will do, go to the page you want to edit on the website. Click on “Edit me” pencil icon , shown next to the page title. If you want to add a new page, the editors will give you the link to the page via comments in the issue you created. The page will come with a predefined template, based on the kind of content you want to contribute.
2. The “Edit me” pencil icon will take you to the GitHub repository, where you again click on the pencil icon, shown on the right, and start editing.

   

3. You can now edit or add new text and images according to the provided template. GitHub provide a guide for writing and formatting in GitHub. We also provide a markdown cheat sheet to show you how to write in this webpage. Make sure to read our style guide before start writing. In general, try to avoid manual interlinking of Training SPLASH pages.
4. If you have mentioned tools or resources in your text, make sure to add them to the tool and resource list. If you want to list training material in your page, add it to the metadata of the page, according to the training matadata fields provided in the page template.
5. When you are happy with your first draft of the content, go to the “Propose changes” section at the end of the page and write a title and a brief explanation of your changes.
6. Click on “Propose changes”.

   

7. You are now redirected to the Pull Request ( PR Pull Request
   ) page. A “pull request” is a request to “pull” your changes into the website. Click on the “Create Pull Request” green button. Here you can choose to:
   • “Create draft pull request”: choose this if you have not finished writing. Later on you can always click on “Ready for review” to switch to a normal pull request. You can find more information about draft pull requests in the GitHub documentation.
   • “Create pull request”: choose this if you have finished your text. Editors will then review your request.

     

8. In the description of your pull request you can link to the issue that relates to this change by typing a hashtag # and the correct issue number. Suggestions will appear. This way it is easy for the editors to link back the issue were this change might have been discussed beforehand.

   

9. You can return to your pull request by going to the pull request section of our GitHub repo.

10. If you change your mind about anything in your pull request and the request is not closed, or if the editor tells you to edit your request during the review process, you have to:
    • Go to your pull request
    • Click on “Files changed” in the top menu bar.

      

    • Click on the icon with 3 dots “…” of the file you want to edit and then click on “Edit file”.

      

    • Make your changes.
    • Click on “Commit changes”.

Request a review

If you open a normal pull request then a review is automatically requested. The relevant editors will check your changes. If your request is still in draft, click on “Ready for review” to request a review. You can find more information about draft pull requests in the GitHub documentation.

Address editors’ comments

1. When editors add comments or add a review of your pull request, you will be notified.
2. You need to address editors’ comments and requests by editing your pull request as in step 7 (see above).
   • Go to your pull request
   • Click on “Files changed” in the top menu bar.

     

   • Click on the icon with 3 dots “…” of the file you want to edit and then click on “Edit file”.

     

   • Make your changes.
   • Click on “Commit changes”.
3. When all the requests have been addressed, the editors will mark the conversation as “Resolved” and the proposed changes as “Approved”.
4. You content is ready to be merged and published in the main website.
5. Editors publish your content.