Merged badge favicon for MRs ?

Problem to solve

As well as the pipeline running, build failed and build success badges, I think it would ace to have an additional badge to indicate the MR has been merged.

Current icons

Blue 'pie chart' (pipeline running)

Green tick (success)

Red cross (failure)

Proposed new 'merged MR' icon

Perhaps a purple tick or M (or something unique) to reflect the MRs new state of being merged, e.g.

Relevant links

Original proposal - https://gitlab.com/gitlab-org/gitlab-ce/issues/45239

added Create [DEPRECATED] devopscreate merge requests and removed ~2278654 labels

@jramsay ~"Accepting Merge Requests" here?

added [deprecated] Accepting merge requests label

changed milestone to %Backlog

@ashmckenzie can you be more specific as to which exact states need favicon? I would like to take this up as a part of community contribution

The state I was thinking of was 'MR merged'. So once a MR is merged, the icon goes from being either a green tick (success) or red cross (failure) to perhaps a purple M (or something unique) to reflect the MRs new state of being merged.

@ashmckenzie that's a great idea, will enable user to navigate with ease across multiple open tabs. I would like to take this up as part of community contrib

changed title from Merged badge favicon for MR's ? to Merged badge favicon for MRs ?

It seems this is a dup of #45239 (closed)?

This would also have to entie with https://gitlab.com/gitlab-org/gitlab-ce/issues/35006#note_34822532 and !14497 (merged)

changed the description

It seems this is a dup of #45239 (closed)?

Right you are @almereyda

changed the description

marked #45239 (closed) as a duplicate of this issue

marked this issue as related to #57963 (closed)

mentioned in issue #57963 (closed)

changed the description

I think it makes sense to remove the status icon from the favicon altogether if the MR has been merged, rather than adding an additional icon.

@annabeldunstone that would be a different state (which is a good thing), but IMHO would be too easily confused with an Issue as Issues don't have any icon.

added groupsource code label

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue