Gitlab 9.5 released(about.gitlab.com)
about.gitlab.com
Gitlab 9.5 released
https://about.gitlab.com/2017/08/22/gitlab-9-5-released/
7 comments
It wouldn't surprise me at all if subkeys got missed in v1 of the feature, it's rare to use gpg, and even rarer to use subkeys :)
I'm sure if you file a bug with the details, they'll sort it it!
I'm sure if you file a bug with the details, they'll sort it it!
Looks like someone beat me to it!
https://gitlab.com/gitlab-org/gitlab-ce/issues/36829
https://gitlab.com/gitlab-org/gitlab-ce/issues/36829
One of the main reasons we aren't using GitLab for our open source projects is the network effect that GitHub enjoys. We work openly on GitHub, and many of our stakeholders have GitHub accounts.
Are there any ways to manage a federated project, using GitLab as the primary project management while still maintaining presence in the GitHub community?
Are there any ways to manage a federated project, using GitLab as the primary project management while still maintaining presence in the GitHub community?
GitLab allows users to sign in using their GitHub accounts.
It solves the `everyone has a GitHub account` problem.
Not really, if "SamHouston" (not a real person, just example) has a Github account but has yet to sign up/in with Gitlab, I cannot ping that person via a comment on Gitlab no?
Could you have Github as a mirror but without issues and PRs, and handle those at Gitlab? That way you at least show up in searches.
Examples:
https://gitlab.com/jakebasile/gpg-sign-test/commits/master
https://github.com/jakebasile/gpg-sign-test/commits/master
Edit: it is possible I am just doing something wrong, I don't routinely sign commits. But seeing as the exact same commit in GitHub shows as verified I think there is a problem here.