<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><br></div><div dir="ltr"><br>On 10 Feb 2019, at 2:37 am, Eric F (iEFdev) <<a href="mailto:eric@iefdev.se">eric@iefdev.se</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<p><font face="Arial">Thanks Zero.</font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2/10/19 2:39 , Zero King wrote:<br>
</div>
<blockquote cite="mid:20190210013916.3fxyvtesmgtszbo5@macports.org" type="cite">I believe the maintainers field is used to contact the
maintainer, <br>
either via email or by mentioning (@) the user on GitHub. We can't
<br>
contact one with their GitLab or Bitbucket account in our PRs or
Trac <br>
tickets, so I think other Git hosting services are not relevant
here. <br>
</blockquote>
Yes, I see your point in that. So, it's for the MP bot to be able to
assign PR's automatically, for example?<br>
Maybe I was thinking more from a user prespective. If port info
returns my email and my GitLab handler, then they know where to find
both me, and prob the code. Or if that could be used as an
additional entry?<br>
<br>
<blockquote cite="mid:20190210013916.3fxyvtesmgtszbo5@macports.org" type="cite">
If in the future we switch to another service for issue/PR
tracking, we <br>
may adopt a transitional scheme like this though.
</blockquote>
Speaking of that… Are there any plans to expand to GitLab? They have
a great function to import/mirror from GitHub, which keep the repo
updated.<br></div></blockquote><div><br></div>What do you mean by expand to gitlab?. We have<div><br></div><div><a href="https://github.com/macports/macports-ports/pull/3510">https://github.com/macports/macports-ports/pull/3510</a></div><div><br></div><div>Which discusses adding a new port group for gitlab, or perhaps extending the github one to support other hosts.</div><div><br></div><div> Chris</div><div><br><blockquote type="cite"><div dir="ltr">
<br>
I know when everyone <i>“fled”</i> to GitLab last year… there were
a few articles how to intergrate the two. I don't remember though if
it was possible to manage PR/issues from one and sync with the
other. Couldn't find the articles I read back then, but a quick
search now:<br>
<br>
- <a class="moz-txt-link-freetext" href="https://medium.com/@an0xff/gitlab-loves-github-c5ec797f7814">https://medium.com/@an0xff/gitlab-loves-github-c5ec797f7814</a><br>
- <a class="moz-txt-link-freetext" href="https://docs.gitlab.com/ee/integration/github.html">https://docs.gitlab.com/ee/integration/github.html</a><br>
-
<a class="moz-txt-link-freetext" href="https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/github_integration.html">https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/github_integration.html</a><br>
<br>
<br>
<i>Ok, I'll keep the patch (</i><i><a href="https://gist.github.com/iEFdev/fedaf1dea83b07d053b70956cd761675">»»</a></i><i>)
for later then.</i><br>
<br>
· Eric<br>
</div></blockquote></div></body></html>