Skip to content

ci: generate contributors automatically monthly #3250

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

Merged
merged 1 commit into from
Apr 6, 2021
Merged

ci: generate contributors automatically monthly #3250

merged 1 commit into from
Apr 6, 2021

Conversation

JounQin
Copy link
Contributor

@JounQin JounQin commented Mar 31, 2021

related to #3064 (review)

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @JounQin!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@bradzacher bradzacher requested a review from JamesHenry April 1, 2021 01:24
@JounQin
Copy link
Contributor Author

JounQin commented Apr 6, 2021

cc @JamesHenry Any news?

Copy link
Member

@JamesHenry JamesHenry left a comment

Choose a reason for hiding this comment

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

Great, thanks @JounQin!

@JamesHenry JamesHenry merged commit e6f0698 into typescript-eslint:master Apr 6, 2021
@JounQin JounQin deleted the ci/workflows branch April 6, 2021 07:12
@JounQin
Copy link
Contributor Author

JounQin commented May 1, 2021

https://github.com/typescript-eslint/typescript-eslint/runs/2480548262?check_suite_focus=true#step:9:9

@JamesHenry It seems broken due to protected branch, should it be allowlisted or create a PR automatically instead?

@JamesHenry
Copy link
Member

Thanks @JounQin I'll make some updates to it

@JamesHenry
Copy link
Member

I have managed to use the create-pull-request action to work around the protected branch point. As part of that I had to switch the token used to the existing PAT because the built in token by design does not trigger any subsequent checks: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#triggering-further-workflow-runs

Here is an example of the output of the action: #3343

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants