@fastlane-bot migration to GitHub Actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, javascript
Research direction
Start by reviewing the GitHub Actions migration proposal and the existing checked-off actions linked in this issue to understand the intended behavior and conventions. The remaining scope is the unchecked Slack notification for pull requests labeled status: needs-attention; done means implementing and activating that action, with its behavior documented.
Written by the indexing model from the issue text.
Description
Introduction
Based on the proposal, we would like to migrate to GitHub Actions. This will bring a bunch of improvements:
- well tested and small, single job focused code (an action)
- bot's reactiveness improvements (by using web hooks)
- easier contribution
- no need for running a dedicated server for a bot
- there are plenty of actions ready to be used in production, i.e. stale
- switching the mindset from
fastlane botcode to reusable and useful for others - bot's icon and messages improvements
- documentation
GitHub Actions to be implemented and activated
We will need to implement the following actions:
- Asking about
fastlane envinformation - Marking a PR as merged:
- saying thank you for a contribution
- adding
status: included-in-next-releaselabel to the PR - removing
status: needs-attentionlabel from the PR
- Marking a PR as released:
- informing about including the changes from a PR in a release
- adding a comment to the referenced issue that the PR has been released
- adding
status: releasedlabel to the PR - removing
status: included-in-next-releaselabel from from the PR
- Locking closed issues and pull requests that have not had recent interaction
- Sending a message to Slack channel about PRs that have
status: needs-attentionlabel
Anyone is more than welcome to help 🙌 Please open a new issue for an action you'd like to implement and link it to this very issue.
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 9
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastlane/github-actions
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
fastlane/github-actions#17 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
fastlane/github-actions#13 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
fastlane/github-actions#11 ·
All issues in fastlane/github-actions
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·