workflow to do automated update of dependencies#137
Open
d-honeybadger wants to merge 1 commit into
Open
Conversation
d-honeybadger
force-pushed
the
dkomsa/cursor-workflows
branch
2 times, most recently
from
acdfcdd to
132aba4
Compare
d-honeybadger
force-pushed
the
dkomsa/cursor-workflows
branch
from
132aba4 to
bf0e6de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It raised a reasonable PR: #138 (ignore the added update.yml wf it's just case the workflow was running off of my branch rather than main, which is not going to be an issue when the workflow is triggered properly, with workflow_dispatch off of main branch
Only change necessary to make this more production-ready is to replace my cursor API key with some team-owned one.
Would be extra helpful in the repos where update steps are complex (like csi)