Skip to content
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

gh-428: Add GitHub issue to description of PR #430

Merged
merged 19 commits into from
Jun 16, 2022
Merged

gh-428: Add GitHub issue to description of PR #430

merged 19 commits into from
Jun 16, 2022

Conversation

ryanlong1004
Copy link
Contributor

@ryanlong1004 ryanlong1004 commented Apr 13, 2022

Closes #428

bedevere/util.py Outdated Show resolved Hide resolved
requirements.txt Outdated Show resolved Hide resolved
tests/test_gh_issue.py Outdated Show resolved Hide resolved
bedevere/util.py Outdated Show resolved Hide resolved
bedevere/util.py Outdated Show resolved Hide resolved
@ryanlong1004 ryanlong1004 requested a review from Mariatta April 13, 2022 03:30
@ambv ambv closed this Apr 13, 2022
@ambv ambv reopened this Apr 13, 2022
@cpython-cla-bot
Copy link

cpython-cla-bot bot commented Apr 13, 2022

All commit authors signed the Contributor License Agreement.
CLA signed

@hugovk
Copy link
Member

hugovk commented May 2, 2022

@ryanlong1004 Please can you resolve the conflicts?

@codecov
Copy link

codecov bot commented May 2, 2022

Codecov Report

Merging #430 (b302bf8) into main (77db0d5) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #430   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           18        18           
  Lines         1720      1760   +40     
  Branches       208       213    +5     
=========================================
+ Hits          1720      1760   +40     
Flag Coverage Δ
Python_3.10 100.00% <100.00%> (?)
Python_3.11-dev 100.00% <100.00%> (?)
Python_3.8 100.00% <100.00%> (?)
Python_3.9 100.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
bedevere/util.py 100.00% <100.00%> (ø)
tests/test_gh_issue.py 100.00% <100.00%> (ø)
tests/test_stage.py 100.00% <100.00%> (ø)
tests/test_util.py 100.00% <100.00%> (ø)
bedevere/news.py 100.00% <0.00%> (ø)

bedevere/util.py Outdated Show resolved Hide resolved
bedevere/gh_issue.py Outdated Show resolved Hide resolved
bedevere/util.py Outdated Show resolved Hide resolved
tests/test_gh_issue.py Outdated Show resolved Hide resolved
ryanlong1004 and others added 4 commits May 7, 2022 18:57
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
bedevere/util.py Outdated Show resolved Hide resolved
@ryanlong1004 ryanlong1004 requested a review from JelleZijlstra May 7, 2022 23:53
BODY = f"""\
{{body}}
gh-{{issue_number}}
{CLOSING_TAG}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there a closing tag but no opening tag?

I'm not sure what the tag is for, but my best guess is that it's so the bot can reliably recognize that it has already added a link. So maybe we should also add an open tag and use that to check whether to add the issue number.

Copy link
Contributor Author

@ryanlong1004 ryanlong1004 May 9, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JelleZijlstra, can this conversation be resolved?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old code did have an opening tag:

<!-- {TAG_NAME}: bpo-{{issue_number}} -->

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though it seems we're not using the tag now. If so, we should remove the closing tag too.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the tag was added there to make it easier to parse it, e.g. if one day we migrate again.

tests/test_gh_issue.py Outdated Show resolved Hide resolved
@Mariatta
Copy link
Member

Thanks for your work @ryanlong1004!

Would you be able to increase the coverage to 100%?

@erlend-aasland erlend-aasland changed the title add github issue to description of PR gh-428: Add GitHub issue to description of PR Jun 15, 2022
@erlend-aasland
Copy link

@Mariatta, you requested changes. Are you happy with the PR as it stands? Please mark it approved, if so.

bedevere/util.py Outdated Show resolved Hide resolved
tests/test_util.py Outdated Show resolved Hide resolved
bedevere/util.py Outdated Show resolved Hide resolved
tests/test_util.py Outdated Show resolved Hide resolved
@ambv ambv merged commit ad03d53 into python:main Jun 16, 2022
@ryanlong1004 ryanlong1004 deleted the 430_add_github_issue_to_description branch June 22, 2022 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add link to the GitHub Issue from the PR
7 participants