[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [trial] getting started

From: Federico Bruni
Subject: Re: [trial] getting started
Date: Tue, 28 Apr 2020 22:50:02 +0200

Il giorno mar 28 apr 2020 alle 09:02, Jonas Hahnfeld <address@hidden> ha scritto:
Am Dienstag, den 28.04.2020, 00:27 +0200 schrieb Federico Bruni:
Il giorno mer 22 apr 2020 alle 14:28, Jonas Hahnfeld <address@hidden> ha scritto:
 > here we go:
 > To reiterate: This is _NOT_ meant for "production" work, just for
 > evaluation. If we decide to fully use GitLab, I'll do a fresh
> migration into the group and archive the test
 > repositories. So feel free to play with it!

 Many thanks for your work!

 I've just started verifying some fixed issues.
One of the most annoying tasks in verifying issues is checking that a
 commit is actually present in the repository and precisely in the
 specific release tag.
I used to do this locally using git, but can't remember how. I've tried
 all these commands without success on commit id of below example.
 Anyway, I'd rather use Gitlab for this check...

 Let's take this issue as example:

 See how Github performs better than Gitlab on this aspect:

Do you know if this can be improved? Or will it work as in Github once
 we migrate?

I guess you're referring to the annotation, that this commit is
included in release/2.21.0-1? Incidentally GitLab does have the same
feature if you click the ellipsis dots. But it's bailing out because
there are "too many tags"...

I did click on the three dots, but no tag is shown.
I guess it's a Gitlab bug.

However for the purpose of verification (if we want to continue doing
this) I think you can use the Compare functionality:
which is not in release/2.21.0-1

Doesn't seem what I was looking for.
Anyway, if we switch to GitLab, commit verification won't be needed anymore.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]