- 🎨 when improving the format/structure of the code
- 🚀 when improving performance
- ✏️ when writing docs
- 💡 new idea
- 🚧 work in progress
- ➕ when adding feature
- ➖ when removing feature
- 🔈 when adding logging
- 🔇 when reducing logging
- 🐛 when fixing a bug
cfhdojbkjhnklbpkdaibdccddilifddb Adblock Plus 10000000 | |
gighmmpiobklfepjocnamgkkbiglidom AdBlock 10000000 | |
efaidnbmnnnibpcajpcglclefindmkaj Adobe Acrobat 10000000 | |
gomekmidlodglbbmalcneegieacbdmki Avast Online Security 10000000 | |
eofcbnmajmjmplflapaojjnihcjkigck Avast SafePrice 10000000 | |
chfdnecihphmhljaaejmgoiahnihplgn AVG Web TuneUp 10000000 | |
flliilndjeohchalpbbcdekjklbdgfkk Avira Browser Safety 10000000 | |
gpdjojdkbbmdfjfahjcgigfpmkopogic Pin It Button 10000000 | |
lifbcibllhkdhoafpjfnlhfpfgnpldfl Skype 10000000 | |
mallpejgeafdahhflmliiahjdpgbegpk FromDocToPDF 9298905 |
This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.
A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:
- It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
- It is free, with no quotas.
- Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.
Sometimes you want to have a subdirectory on the master
branch be the root directory of a repository’s gh-pages
branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master
branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist
.
Remove the dist
directory from the project’s .gitignore
file (it’s ignored by default by Yeoman).