- Go to the play-bucket repository.
- Create a new file or edit an existing file through the Fork workflow. Propose your changes and open a pull request, so it can be accepted and merged.
Advanced: now let us simulate a merge conflict 😉
- Create a new repository on your GitHub profile: https://github.com/{your-profile-name}?tab=repositories.
- Create a few Markdown files, including README.md. You can use https://jaspervdj.be/lorem-markdownum to generate content.
- Link your files one to another. Broken links are very welcome as they will be used in the next exercise of the script.
- Go to the Settings tab of your repository.
- In the GitHub Pages section select a source to enable GitHub Pages.
- Choose the theme you like the most.
Take a look at this example of a GitHub Page enabled for this script.
Continuous integration is a way of automating processes around your project.
- Enable Travis to gain access to your repository: https://travis-ci.org/profile/.
- Create such a .travis.yml file in the root of your repository. To get more understanding of the tool used here for links validation, read its docs: https://github.com/dkhamsing/awesome_bot.
- Check how your CI plan is doing: https://travis-ci.org/profile-org-name/repo-name.
- Add the following badge at the top of your README:
[![Build Status](https://travis-ci.org/profile-org-name/repo-name.svg?branch=master)](https://travis-ci.org/profile-org-name/repo-name)
- Enable CircleCI to gain access to your repository: https://circleci.com/signup/.
- Create such a config.yml file in a new .circleci directory.
- Check how your CI plan is doing: https://circleci.com/gh/profile-org-name/repo-name.
- Add the following badge at the top of your README:
[![CircleCI](https://circleci.com/gh/profile-org-name/repo-name/tree/master.svg?style=svg)](https://circleci.com/gh/profile-org-name/repo-name/tree/master)
https://github.com/georgebina/ghd-wiki repository presents how to do:
- Markdown mixed with DITA
- CI automation using TravisCI
- GitHub pages
- Crowdsourcing