-
Notifications
You must be signed in to change notification settings - Fork 7
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
Enable Danger #714
Comments
@jdauphant is that plan ok for you? |
We can add Danger support, for access token, it should not be linked to individual account. |
@pseudonyme21 is on working on similar things on thap-infra repository |
@pseudonyme21 I let you check our suggestion |
We prefere using Github Apps |
@jdauphant we agree with you according to https://docs.github.com/en/developers/apps/getting-started-with-apps/about-apps. But it seems not possible to use GH apps with Danger : danger/danger-js#1199 How do you want to proceed ? which actions should we plan and who should work on them?
@bmarty Did you consider the Github Apps option when you set up Danger for Element-Android? I think we should consider this option for Element, if this was not done yet. |
No. |
Element-Android v1.4.32 integrates Danger in the CI build process.
Danger is a CI tool automating some common code reviews. It can check that a reviewer has been assigned to a PR, run the code quality checks (
Lint
,ktlint
,Detekt
…) and much more by adding plugins to the process.A bot will then post a comment in the PR in case of failure.
Since Tchap-Android has been rebased on that version, we have to configure Danger to restore some CI steps.
It requires the creation of a new Github account (eg.
TchapBot
) to check all the Tchap PRs, like Element does.It does not require adding the bot to the Tchap organization, just the creation of an access token scoped to
public_repo
as described in the Danger guide.The text was updated successfully, but these errors were encountered: