fastlane / github-actions Goto Github PK

Enable fastlane-env-reminder action on fastlane main repository.

Currently there is a default pr-comment message for communicate-on-pull-request-merged Action:

The message does not contain congrats for a pull request author. Below you will find an original message:

To avoid ambiguity, we should delete a default message from an Action and make it required instead.

The workflow file will look like this then:

name: Processing merged pull requests
on: 
  pull_request:
    types: [closed]

jobs:   
  communicate-on-pr-merged:
    name: Communicate on pr merged
    runs-on: ubuntu-latest    
    steps:
    - uses: actions/checkout@master
      with:
        ref: refs/heads/master
    - uses: fastlane/github-actions/communicate-on-pull-request-merged@latest
      with:
        repo-token: "${{ secrets.BOT_TOKEN }}"
        pr-comment: "Hey @${{ github.event.pull_request.user.login }} :wave:\nThank you for your contribution to _fastlane_ and congrats on..."

List of issues that triggered the bot although env info was provided:

Issue Description

Add GitHub Action that will mark a pull request as released. The action should:

• add a comment to the pull request about including the changes in a release

Congratulations! 🎉 This was released as part of fastlane x.y.z 🚀

• add status: released label to the pull request and remove status: included-in-next-release label from it
• add a comment to the referenced issue that the pull request has been released

The pull request #xxxxx that closed this issue was merged and released as part of fastlane x.y.z 🚀
Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!

reference to the epic: #3.

fastlane-env-reminder is delivered as a container and run with docker. Check container-toolkit-action to see an action setup.

Hey guys,

It's weird this seems to the label status: included-in-next-release to my PR by default. How do I prevent that? (it's not applicable to me)

Details:

• The PR in question: benwinding/firecache#2
• The Workflow file: https://github.com/benwinding/firecache/blob/07a28443abbb8b9d5a550872585547edcc7447d3/.github/workflows/deploy.yml#L38-L44
• The Workflow Run: https://github.com/benwinding/firecache/runs/593964258

The PR:
benwinding/firecache#2

The run
https://github.com/benwinding/firecache/runs/593964258
Looks like this is where the defaults are added?

How can I stop that?

Thanks for open-sourcing your project, works really well 👌

Cheers,
Ben

Issue Description

Add GitHub Action that will mark a pull request as merged. The action should:

• add a comment to a pull request saying thank you to a contributor for a contribution

• add status: included-in-next-release label to the PR

reference to the epic: #3.

See #10 for example, it would be awesome if we could clean up the comment (hide as outdated, or delete) if the information was added as required (or posted in a follow up comment by the same user)

See the checks for the last commit of master:

That doesn't really look right.

Identify which code paths were added, automatically add labels.

(Counter argument: no label means untriaged, adding labels automatically will break this.)

Currently runs as @github-actions:

See screenshot:
fastlane/fastlane#15305 (comment)

Could be @fastlane-bot maybe.

Issue Description

Some time ago GitHub has announced GitHub Actions. Recently fastlane organisation got an access to Actions Beta. It is a good time to start playing with the new feature from GitHub.

Based on the proposal about @fastlane-bot V2:

What does the bot do?

...
Asking about fastlane env information

☝️ seems to be a good candidate to start with.

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 bot code 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 env information
• Marking a PR as merged:
  • saying thank you for a contribution
  • adding status: included-in-next-release label to the PR
  • removing status: needs-attention label 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: released label to the PR
  • removing status: included-in-next-release label 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-attention label

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.

Update the README file:

• an introduction about what the repository is;
• the development workflow: step by step instruction to create a new GitHub Action in this repository, the release process, the branching model;
• the list of the actions available in this repository.