Skip to content

CI: trigger lockfile CI automatically on dependabot PRs#3646

Merged
superlopuh merged 13 commits intomainfrom
dependabot/bleep/bloop
Jan 6, 2025
Merged

CI: trigger lockfile CI automatically on dependabot PRs#3646
superlopuh merged 13 commits intomainfrom
dependabot/bleep/bloop

Conversation

@superlopuh
Copy link
Copy Markdown
Member

No description provided.

@codecov
Copy link
Copy Markdown

codecov bot commented Dec 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.31%. Comparing base (f06d74e) to head (463876d).
Report is 14 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3646      +/-   ##
==========================================
+ Coverage   91.30%   91.31%   +0.01%     
==========================================
  Files         466      467       +1     
  Lines       58375    58531     +156     
  Branches     5626     5643      +17     
==========================================
+ Hits        53297    53449     +152     
- Misses       3630     3632       +2     
- Partials     1448     1450       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@superlopuh
Copy link
Copy Markdown
Member Author

please update lockfile

1 similar comment
@superlopuh
Copy link
Copy Markdown
Member Author

please update lockfile

@superlopuh
Copy link
Copy Markdown
Member Author

please update lockfile

superlopuh added a commit that referenced this pull request Dec 16, 2024
…#3647)

I tested it [here](#3646) and it
works if you do the dumb thing and trigger on push, but it seems to not
run actions on unsigned commits by default. I'm hoping that if we
trigger the action manually it'll inherit the clicker's permissions and
re-run the action. In either case, I think whatever we adopt should
supercede the cron job one as we want to never be out of sync between
the pyproject and lockfile.
@superlopuh superlopuh changed the title [WIP] test dependabot uv update #3645 CI: trigger lockfile CI automatically on dependabot PRs Jan 6, 2025
@superlopuh superlopuh self-assigned this Jan 6, 2025
@superlopuh superlopuh added the CI Continuous Integration label Jan 6, 2025
Copy link
Copy Markdown
Collaborator

@alexarice alexarice left a comment

Choose a reason for hiding this comment

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

13 commits, 3 lines changed

@superlopuh superlopuh merged commit 242db62 into main Jan 6, 2025
@superlopuh superlopuh deleted the dependabot/bleep/bloop branch January 6, 2025 16:09
Copy link
Copy Markdown
Collaborator

@compor compor left a comment

Choose a reason for hiding this comment

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

So we'll have to close and open dependabot PRs to have this triggered?

@alexarice
Copy link
Copy Markdown
Collaborator

The lockfile update should hopefully trigger automatically, but you'll have to reopen to get the normal ci to trigger on the commit that the update-lockfile-bot makes

Copy link
Copy Markdown
Collaborator

@EdmundGoodman EdmundGoodman left a comment

Choose a reason for hiding this comment

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

lgtm - is there a place we should document the process for what needs to happen with dependabot PRs, or can we just leave it as institutional knowledge and hope dependabot supports uv soon?

@compor
Copy link
Copy Markdown
Collaborator

compor commented Jan 6, 2025

lgtm - is there a place we should document the process for what needs to happen with dependabot PRs, or can we just leave it as institutional knowledge and hope dependabot supports uv soon?

This is a great point - maybe a section "For maintainers" in the README? Or an open issue to track this and the workaround?

@superlopuh
Copy link
Copy Markdown
Member Author

IDK, uv is now used by 13% of PyPI packages, I assume it's going to be fixed soon enough that just telling people what to do should be OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants