Changes between Version 3 and Version 4 of user/catalyst


Ignore:
Timestamp:
Oct 7, 2017, 3:52:25 AM (2 years ago)
Author:
catalyst
Comment:

repo sync stuff

Legend:

Unmodified
Added
Removed
Modified
  • user/catalyst

    v3 v4  
    3333Sep 19 16:56:50.000 [info] onion_populate_cpath(): Generating cpath hop failed.
    3434}}}
     35
     36== GitLab and GitHub repo sync notes ==
     37
     38GitLab.com [https://gitlab.com/help/workflow/repository_mirroring.md supports] pull and push sync (one of each per repository).  This needs an access token for push (at least over HTTPS; push mirroring over SSH doesn't seem to be supported).  GitLab Community Edition doesn't support mirroring; that's an Enterprise Edition thing.  It's possible to configure CI pipelines to do it, but it's somewhat less friendly.  On the other hand, the built-in mirroring isn't configurable to force-update refs, which a custom pipeline would be able to do.
     39
     40=== Deploy keys, etc ===
     41
     42[https://gitlab.com/help/ssh/README.md#deploy-keys GitLab] and [https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys GitHub] both support SSH deploy keys.  These default to read-only on GitLab, and read-write on GitHub.  Deploy keys are per-repository.
     43
     44GitLab has [https://gitlab.com/help/api/README.md#private-tokens Private Tokens] and [https://gitlab.com/help/user/profile/personal_access_tokens.md Personal Access Tokens].  Private Tokens are for API use and supposedly allow full API access as you, but don't seem to provide push access over HTTPS.  Access Tokens (with `api` scope) apparently do provide push access over HTTPS.  GitHub doesn't have Private Tokens, but does have [https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/ Access Tokens].