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

Squash on green (again) #166

Merged
merged 2 commits into from
Sep 11, 2020
Merged

Squash on green (again) #166

merged 2 commits into from
Sep 11, 2020

Conversation

ashfurrow
Copy link
Contributor

Successor to #161 and #164. I'm self-assigning so I can monitor once merged /cc @jonallured

The important change is in 83f950f.

@ashfurrow ashfurrow self-assigned this Sep 11, 2020
@ashfurrow ashfurrow merged commit 4caaa6a into master Sep 11, 2020
@ashfurrow ashfurrow deleted the squash-on-green-fix-2 branch September 11, 2020 19:40
@ashfurrow
Copy link
Contributor Author

Okay so this is failing in the weirdest way. The process of applying the Squash on Green label was failing in Danger's createOrAddLabel function with the following API response:

{ resource: 'Label', code: 'already_exists', field: 'name' }

Looks like we were hitting this bug, which has been fixed in Danger already (but we're on an older version): danger/danger-js#1020 Basically we weren't paginating through all the labels on a repo, so it didn't see the (most-recently created) "Squash on Green" label already existed.

I deleted some unused labels in Eigen and it's working now 🎉 I will ask for a pairing partner on Monday's standup to upgrade to the latest Danger, which should solve this problem generally.

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.

2 participants