Verbatim is committing surpisingly many merge commits

NEW
Unassigned

Status

5 years ago
3 years ago

People

(Reporter: clouserw, Unassigned)

Tracking

Details

(Reporter)

Description

5 years ago
It looks like moz-verbatim is committing to more than just L10n files.  It's doing merge commits and stuff.  I've seen it once a while ago, this is the most recent example:

https://github.com/mozilla/fireplace/compare/fd52b54334...8afba161cc

It should only be touching .po files
Component: Other → Verbatim
Product: Mozilla Localizations → Webtools
Version: unspecified → other

Comment 1

5 years ago
Can you detail on what's happening? I look at the comparison, and it claims that it changed two files. It'd be helpful to learn what you're expecting.

Please file bugs in the verbatim component, this is not about unknown localizations.
(Reporter)

Comment 2

5 years ago
I'm not expecting those 8 merge commits to be there.  The sum total is that it changed those two files, but it did it with a bunch of merge commits cluttering up the history.

Comment 3

5 years ago
Resummarizing.

Dwayne, have concerns like this been raised in other setups, or is that something we're doing?

Here's my speculation: For some reason, we have a merge commit in the local repo, but don't push that. At that point, everytime that a localizer goes in and updates from VCS, we get a merge of that merge.

If that's true, can we avoid having local merge commits around without pushing them upstream?
Flags: needinfo?(dwayne)
Summary: Verbatim is committing more than just L10n → Verbatim is committing surpisingly many merge commits

Comment 4

5 years ago
Axel,

Haven't seen this in any other setup.  We introduced the separate VCS_DIRECTORY in 2.5 so we should have a clean checkout in that directory which should never have any kind of merge conflict.  Since we update that repo then export what we want to commit, then commit.

I guess there is the possibility that between an update and a commit a change could happen upstream in which case we might get a merge commit (this is me as a non-Git expert speaking).

The first step, I think, is to check the repo in VCS_DIRECTORY to see if it is in some odd state.  If it is then I think we can try the next steps which is to clean that up. We might want to change Pootle to prevent that happening again.  If it is OK we'll need to look elsewhere.
Flags: needinfo?(dwayne)

Comment 5

5 years ago
Matjaz, can you check on Dwayne's suggestions?
Flags: needinfo?(m)
Yes. I checked the fireplace repo and everything looks fine ATM:

[verbatim@verbatim1 fireplace]$ git status
# On branch master
nothing to commit (working directory clean)
Flags: needinfo?(m)
(Assignee)

Updated

3 years ago
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.