3 ms·

because on github everyone sees when I make stupid commits to fix my stupid typos

• isacikgoz 8y ago
  pro tip: squash (rebase) your commits then force push to remove "fix typo" history
  • profalseidol 8y ago
    pro tip: be careful in using force push. In the past there's a version of git where it defaults to force all your local branches into the remote copy. When I did use force push, it pushed everything including my outdated local copy of PROD. Fortunately we were able to fix this before somebody else ran a git pull. the new versions I believe are configured safer now afaik.
  • pferde 8y ago
    An even "proer" tip: rebase your commits into something coherent BEFORE pushing, and you can drop the "force".
• the_common_man 8y ago
  aren't private repos free now?
  • kryptiskt 8y ago
    For some reason Pages must still be backed by a public repo for free accounts.
    • davnicwil 8y ago
      On Gitlab you can host pages backed by their free private repos, and also if required you can use their free integrated CI to run any static site generator build step you might have. It's a really good plaform for hosting a blog for free with the 'publish on git push' workflow mentioned above.
      • dsumenkovic 8y ago
        Here are some more details about it https://about.gitlab.com/2016/04/07/gitlab-pages-setup/ https://about.gitlab.com/2016/04/07/gitlab-pages-setup/ and https://docs.gitlab.com/ee/user/project/pages/introduction.html https://docs.gitlab.com/ee/user/project/pages/introduction.h...