After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796395 - Misleading message when committing to stable branches
Misleading message when committing to stable branches
Status: RESOLVED NOTGNOME
Product: sysadmin
Classification: Infrastructure
Component: Git
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2018-05-25 08:38 UTC by Milan Crha
Modified: 2018-05-29 12:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2018-05-25 08:38:39 UTC
When committing to the master branch, I get a clean response:

> [evolutionews]$ git push
> Counting objects: 6, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (6/6), done.
> Writing objects: 100% (6/6), 855 bytes | 855.00 KiB/s, done.
> Total 6 (delta 5), reused 0 (delta 0)
> To gitlab.gnome.org:GNOME/evolution-ews.git
>    47cc16f4..4b879e48  master -> master

but when I commit into the stable branch, in this case origin/gnome-3.28:

> [evolutionews]$ git push
> Counting objects: 6, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (6/6), done.
> Writing objects: 100% (6/6), 861 bytes | 861.00 KiB/s, done.
> Total 6 (delta 5), reused 0 (delta 0)
> remote: 
> remote: To create a merge request for gnome-3-28, visit:
> remote:   https://gitlab.gnome.org/GNOME/evolution-ews/merge_requests/new?merge_request%5Bsource_branch%5D=gnome-3-28
> remote: 
> To gitlab.gnome.org:GNOME/evolution-ews.git
>    a24562f6..d4eb2b06  gnome-3-28 -> gnome-3-28

That "remote" message is misleading, the merge request is a nonsense, because the commit just landed into the place it suggests me to do the merge request for. I do not know what logic is behind that message, but it requires to be updated. At least from my point of view.
Comment 1 Carlos Soriano 2018-05-29 12:34:16 UTC
This comes from upstream GitLab hooks. Can you report upstream and see if they have planned a way to configure that?
Comment 2 Milan Crha 2018-05-29 12:46:05 UTC
Filled https://gitlab.com/gitlab-org/gitlab-ce/issues/46926