-
Notifications
You must be signed in to change notification settings - Fork 4
Move linked issues adjacent to their linked PRs #14
Conversation
98414a1
to
db6bf8a
Compare
db6bf8a
to
47b3263
Compare
0d5550e
to
ca7e2ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm rethinking the value of this PR now since GH doesn't merge the issue and PR. In the Sprint board, we basically have three columns: the one that contains issues, the one that contains PRs and done. Thoughts?
enarx-adjacent-linked-issues
Outdated
# Extract all associated issues from PR commit messages | ||
for c in pr.get_commits(): | ||
for verb, num in regex.findall(c.commit.message): | ||
yield int(num) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to share this function? We use it multiple places. It would probably be useful.
enarx-adjacent-linked-issues
Outdated
content = card.get_content() | ||
if content: | ||
card_cache[content.id] = (card, column) | ||
return card_cache |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Share this code?
ca7e2ce
to
619ab52
Compare
My latest push adds a shared |
619ab52
to
d3caef1
Compare
My latest push fixes a duplicate bug with |
0af3222
to
a213f8e
Compare
8809e49
to
4595105
Compare
We've since moved on from REST API v3, so this will need to be rewritten. Closing in favor of a new PR eventually. |
Adds an action to move issues next to their linked PRs on the sprint board.
Resolves #13.