automate cross-linking between github pull requests and trac issue tickets. #2314

Open
opened 2014-10-07 17:50:17 +00:00 by nejucomo · 2 comments
nejucomo commented 2014-10-07 17:50:17 +00:00
Owner

Wouldn't it be awesome if...

-any time a github pull request were created:

  1. the trac ticket number were parsed from the PR branch name,
  2. If the previous step succeeds update the trac ticket with a link.
  3. If step 1 fails, update the github PR to complain that the branch name is unusual (or even automatically reject it).

There are also probably many other kinds of cross-linking which could be useful, but I prefer specific tickets, so I advocate filing different kinds of cross-linking as unique tickets.

edit: Removed a statement contradicted by the first comment.

*Wouldn't it be awesome if...* -any time a github pull request were created: 1. the trac ticket number were parsed from the PR branch name, 2. If the previous step succeeds update the trac ticket with a link. 3. If step 1 fails, update the github PR to complain that the branch name is unusual (or even automatically reject it). There are also probably many other kinds of cross-linking which could be useful, but I prefer specific tickets, so I advocate filing different kinds of cross-linking as unique tickets. **edit:** Removed a statement contradicted by the first comment.
tahoe-lafs added the
unknown
normal
defect
1.10.0
labels 2014-10-07 17:50:17 +00:00
tahoe-lafs added this to the undecided milestone 2014-10-07 17:50:17 +00:00
nejucomo commented 2014-10-07 18:03:48 +00:00
Author
Owner
This search is a start: <https://www.google.com/search?q=trac+github+plugin>
tahoe-lafs added
dev-infrastructure
and removed
unknown
labels 2014-10-17 11:20:35 +00:00
tahoe-lafs modified the milestone from undecided to soon (release n/a) 2014-10-17 11:20:35 +00:00
meejah commented 2021-03-30 18:41:12 +00:00
Author
Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
tahoe-lafs modified the milestone from soon (release n/a) to soon 2021-03-30 18:41:12 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2314
No description provided.