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

Fixing GitLabDSL parsing #283

Merged
merged 3 commits into from
Oct 6, 2019
Merged

Fixing GitLabDSL parsing #283

merged 3 commits into from
Oct 6, 2019

Conversation

fortmarek
Copy link
Member

When adding GitLab support, we stumbled upon some issues when certain keys were missing or did not correspond 1:1, so these are the fixes we applied to get it working.

Also, fixes: #279

Copy link
Member

@f-meloni f-meloni left a comment

Choose a reason for hiding this comment

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

Thank you for the PR, can you please update the CHANGELOG as well? :)

@fortmarek
Copy link
Member Author

Done 👍

@fortmarek
Copy link
Member Author

BTW, I could add check for Changelog to Dangerfile, would you be interested in a such quick PR?

@f-meloni
Copy link
Member

f-meloni commented Oct 6, 2019

@fortmarek that check already exist, I actually wondered why it didn't post here, and it came out that the Danger user need to verify its email in order to post https://travis-ci.org/danger/swift/jobs/593633791#L593

@f-meloni f-meloni merged commit 67d71fd into danger:master Oct 6, 2019
@fortmarek
Copy link
Member Author

Huh, interesting, good to know, thanks for the merge!

@f-meloni
Copy link
Member

f-meloni commented Oct 6, 2019

No problem! The change is not released on 2.0.6

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.

ERROR: Failed to parse JSON (missing allow_collaboration)
2 participants