-
Notifications
You must be signed in to change notification settings - Fork 569
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
Auditing for 6.11.1 #230
Comments
Ran this with the Exact thing I ran:
|
For some reason the first one here (nodejs/node#6308) has the |
it is possible to trip the abuse detection from all the traffic you send if there is a big delta I worked a rate limited queue into branch-diff, you can maybe play with the options on that to avoid triggering the abuse bots... if you start getting requests rejected the filters don't end up working... which can explain why you are getting semver-major things leaking in we could maybe permanently fix this by refactoring branch-diff to use graphql |
So all the ones I've done so far are ones that didn't land cleanly on v7.x, so someone commented saying "please backport", and then nothing happened. I'll put |
Splitting into multiple parts so the tickbox checking doesn't get too slow Part 2:
|
Part 3:
|
Part 4:
|
Part 5:
|
Part 6:
|
Part 7
|
Been watching you're WG meeting... How can I help? |
I don't think the |
@MylesBorins I can see that you are posting a lot of messages in |
@AndreasMadsen sorry I missed this... was just going through the generic audit. I'll mark them all as don't land from now on |
@MylesBorins I've now added |
This is now done. |
WORKING ON THIS NOW: nobody
My week is pretty hectic, does someone want to take point on starting to prep for 6.11.1?
Todo
branch-diff v6.x-staging upstream/v8.x --exclude-label semver-major,semver-minor,dont-land-on-v6.x,backport-requested-v6.x,backported-to-v6.x,baking-for-lts --filter-release
baking-for-lts
semver-patch commits (added by @gibfahn)The text was updated successfully, but these errors were encountered: