Track issue changes, join labels #319

New Issue

GiteaMirror · 2025-11-02T03:18:22-06:00

GiteaMirror commented

2025-11-02 03:18:22 -06:00

Originally created by @jeppech on GitHub (Feb 3, 2017).

When changing/adding/removing multiple labels at the same time, each "event" is showing on their own seperate line, as show below

Wouldn't it be more cleaner to join all the events, so they're represented in one line instead, like this:

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @jeppech on GitHub (Feb 3, 2017). When changing/adding/removing multiple labels at the same time, each "event" is showing on their own seperate line, as show below ![Multiple tags](https://cloud.githubusercontent.com/assets/3226608/22594619/24b54eb8-ea24-11e6-8471-b0170de81846.png) Wouldn't it be more cleaner to join all the events, so they're represented in one line instead, like this: ![one line labels](https://cloud.githubusercontent.com/assets/3226608/22594708/6fe0361e-ea24-11e6-9526-5a2249d72251.png) <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41633912-track-issue-changes-join-labels?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 03:18:22 -06:00

GiteaMirror closed this issue

2025-11-02 03:18:22 -06:00

GiteaMirror commented

2025-11-02 03:18:23 -06:00

@jeppech commented on GitHub (Feb 3, 2017):

The initial feature PR is #788

@jeppech commented on GitHub (Feb 3, 2017): The initial feature PR is #788

GiteaMirror commented

2025-11-02 03:18:23 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

Could this be done in the UI? having something that reads the event-lines and checks username + "added"/"removed" + time_since and concatenating them?

@bkcsoft commented on GitHub (Feb 12, 2017): Could this be done in the UI? having something that reads the event-lines and checks username + "added"/"removed" + time_since and concatenating them?

GiteaMirror commented

2025-11-02 03:18:23 -06:00

@lunny commented on GitHub (Feb 12, 2017):

If we changed more than two labels, how to display on the UI?

@lunny commented on GitHub (Feb 12, 2017): If we changed more than two labels, how to display on the UI?

GiteaMirror commented

2025-11-02 03:18:24 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

$(".event").each(function(index) {
	curr = $(this);
	p = curr.prev();
	if (p != undefined && p.hasClass("event")) {
		event = "added"
		if ($("span.text", p).text().includes("removed")) {
			event = "removed"
		}
		if ($("span > .time-since", p).text() == $("span > .time-since", curr).text() &&
			$("span.text", curr).text().includes(event)) {
			$("span > .label", curr).after($("span > .label", p));
			p.remove();
		}
	}
});

Screenshot:

Edit: The above code is ugly AF and only serves as a proof-of-concept. If someone makes a PR for this, clean up the code first 😂

@bkcsoft commented on GitHub (Feb 12, 2017): ```js $(".event").each(function(index) { curr = $(this); p = curr.prev(); if (p != undefined && p.hasClass("event")) { event = "added" if ($("span.text", p).text().includes("removed")) { event = "removed" } if ($("span > .time-since", p).text() == $("span > .time-since", curr).text() && $("span.text", curr).text().includes(event)) { $("span > .label", curr).after($("span > .label", p)); p.remove(); } } }); ``` Screenshot: ![2017-02-12-075434_1916x1036_scrot](https://cloud.githubusercontent.com/assets/4726179/22860253/92fc558a-f0f8-11e6-92ab-98c9d2110aca.png) Edit: The above code is ugly AF and only serves as a proof-of-concept. If someone makes a PR for this, clean up the code first 😂

GiteaMirror commented

2025-11-02 03:18:24 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

Hint: If the event-element has class="event label add" instead this would be much easier and cleaner :)

@bkcsoft commented on GitHub (Feb 12, 2017): Hint: If the `event`-element has `class="event label add"` instead this would be much easier and cleaner :)

GiteaMirror commented

2025-11-02 03:18:24 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

And the above code doesn't join if the time-since is different

@bkcsoft commented on GitHub (Feb 12, 2017): And the above code doesn't join if the `time-since` is different ![2017-02-12-080425_1916x1036_scrot](https://cloud.githubusercontent.com/assets/4726179/22860299/f4eee004-f0f9-11e6-8238-8f022fb04379.png)

GiteaMirror commented

2025-11-02 03:18:24 -06:00

@jeppech commented on GitHub (Feb 13, 2017):

This looks good

@jeppech commented on GitHub (Feb 13, 2017): This looks good

GiteaMirror commented

2025-11-02 03:18:25 -06:00

@bkcsoft commented on GitHub (Feb 14, 2017):

We could also turn them into Vue-components now that we use Vue in another place :trollface:

@bkcsoft commented on GitHub (Feb 14, 2017): We could also turn them into Vue-components now that we use Vue in another place :trollface:

GiteaMirror commented

2025-11-02 03:18:26 -06:00

@mbger commented on GitHub (Mar 5, 2018):

Any plans/updates on this one? The current instance over at try gitea io still has the same behavior.

@mbger commented on GitHub (Mar 5, 2018): Any plans/updates on this one? The current instance over at try gitea io still has the same behavior. <img width="649" alt="issuelabels" src="https://user-images.githubusercontent.com/5991861/36968196-1dd5fff0-2062-11e8-8be4-d985b232ebe9.png">

GiteaMirror commented

2025-11-02 03:18:26 -06:00

@lunny commented on GitHub (Mar 5, 2018):

@mbger currently nobody working on this.

@lunny commented on GitHub (Mar 5, 2018): @mbger currently nobody working on this.

GiteaMirror commented

2025-11-02 03:18:26 -06:00

@stale[bot] commented on GitHub (Feb 7, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 7, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:18:26 -06:00

@tonivj5 commented on GitHub (Feb 7, 2019):

Unstale 👍

@tonivj5 commented on GitHub (Feb 7, 2019): Unstale :+1:

GiteaMirror commented

2025-11-02 03:18:26 -06:00

@techknowlogick commented on GitHub (Dec 9, 2020):

this was recently merged, can't find PR for it though right now, but you can see that on try.gitea.io it works.

@techknowlogick commented on GitHub (Dec 9, 2020): this was recently merged, can't find PR for it though right now, but you can see that on try.gitea.io it works.

GiteaMirror referenced this issue

2025-11-02 11:43:33 -06:00

[PR #319] [MERGED] Get rid of bin folder within makefile, enabled TiDB #15303

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#319