Skip to content

Additional External Issue Tracker Naming Style options #3678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
johanhugg opened this issue Mar 16, 2018 · 3 comments
Closed

Additional External Issue Tracker Naming Style options #3678

johanhugg opened this issue Mar 16, 2018 · 3 comments
Labels
issue/stale type/enhancement An improvement of existing functionality

Comments

@johanhugg
Copy link

Description

Right now, Numeric, and Alphanumeric is supported. Numeric extracts the numbers from "#123" and Alphanumeric extracts both the alphabetic and numeric parts together, so for example "TG-123 fixes critical bug", TG-123 is clickable and it puts "TG-123" in the {index} part of the URL. However I propose a third option, where either the numeric part of the "TG-123" example is clickable, or the whole part of "TG-123" but the numeric part is extracted and put in {index}.

Hope this makes sense.

Screenshots

asd

@johanhugg
Copy link
Author

image
This is what I have now, but this is just a modified regex of the Alphanumeric Naming Style.

@lafriks lafriks added the type/enhancement An improvement of existing functionality label Mar 16, 2018
@stale
Copy link

stale bot commented Feb 4, 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 stale bot added the issue/stale label Feb 4, 2019
@stale
Copy link

stale bot commented Feb 18, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Feb 18, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
Attempt to fix go-gitea#3678

(cherry picked from commit 4ffda65)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants