-
Notifications
You must be signed in to change notification settings - Fork 32
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
Renovate + changesets investigation #1493
Comments
72636c
added a commit
to seek-oss/rynovate
that referenced
this issue
Mar 25, 2024
The intent here is to allow Renovate to rebase a branch even if it has a skuba autofix commits that have been pushed. I think this is as simple as hardcoding the fixed bot accounts that we use for this purpose. seek-oss/skuba#1493
AaronMoat
pushed a commit
to seek-oss/rynovate
that referenced
this issue
Mar 25, 2024
The intent here is to allow Renovate to rebase a branch even if it has a skuba autofix commits that have been pushed. I think this is as simple as hardcoding the fixed bot accounts that we use for this purpose. seek-oss/skuba#1493
We can try again when v38 is released: renovatebot/renovate#27992 |
Can we delete Line 74 in 3310e6e
|
Ah nice. Yes, likely, though it means that we're relying on users using rynovate* for it to work nicely. Which, maybe is ok (*unless this makes momentum: seek-oss/renovate-config-seek#21) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Look into:
gitIgnoredAuthors
for the above to not lock the PRs after first commit.gitIgnoredAuthors
for the general SEEK ecosystem in combination with skuba autofixes, to not lock renovate PRs after first commitThe text was updated successfully, but these errors were encountered: