fastlane / github-actions

fastlane is a tool for iOS and Android developers to automate tedious tasks like generating screenshots, dealing with provisioning profiles, and releasing your application.

---

✨ All fastlane docs were moved to docs.fastlane.tools ✨

---

Need Help?

Before submitting a new GitHub issue, please make sure to

• Check out docs.fastlane.tools
• Search for existing GitHub issues

If the above doesn't help, please submit an issue on GitHub and provide information about your setup, in particular the output of the fastlane env command.

Note: If you want to report a regression in fastlane (something that has worked before, but broke with a new release), please mark your issue title as such using [Regression] Your title here. This enables us to quickly detect and fix regressions.

fastlane team

Manu Wallner	Joshua Liebowitz	Danielle Tomlinson	Satoshi Namai	Felix Krause
Łukasz Grabowski	Maksym Grebenets	Fumiya Nakamura	Jérôme Lacoste	Stefan Natchev
Helmut Januschka	Manish Rathi	Max Ott	Jimmy Dee	Roger Oba
Iulian Onofrei	Josh Holtz	Daniel Jankowski	Andrew McBurney	Jan Piotrowski
Luka Mirosevic	Kohki Miki	Aaron Brager	Olivier Halligon	Jorge Revuelta H
Matthew Ellis

Special thanks to all contributors for extending and improving fastlane.

Contribute to fastlane

Check out CONTRIBUTING.md for more information on how to help with fastlane.

Code of Conduct

Help us keep fastlane open and inclusive. Please read and follow our Code of Conduct.

Metrics

fastlane tracks a few key metrics to understand how developers are using the tool and to help us know what areas need improvement. No personal/sensitive information is ever collected. Metrics that are collected include:

• The number of fastlane runs
• A salted hash of the app identifier or package name, which helps us anonymously identify unique usage of fastlane

You can easily opt-out of metrics collection by adding opt_out_usage at the top of your Fastfile or by setting the environment variable FASTLANE_OPT_OUT_USAGE. Check out the metrics code on GitHub

License

This project is licensed under the terms of the MIT license. See the LICENSE file.

This project and all fastlane tools are in no way affiliated with Apple Inc. This project is open source under the MIT license, which means you have full access to the source code and can modify it to fit your own needs. All fastlane tools run on your own computer or server, so your credentials or other sensitive information will never leave your own computer. You are responsible for how you use fastlane tools.

---

✨ All fastlane docs were moved to docs.fastlane.tools ✨

---

github-actions's Issues

Update `fastlane-env-reminder` to use fastlane-bot account

Currently runs as @github-actions:

See screenshot:
fastlane/fastlane#15305 (comment)

Could be @fastlane-bot maybe.

Update README file

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.

Adds label ''status: included-in-next-release" by default

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

Remove a default `pr-comment` message from `communicate-on-pull-request-merged`

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

github-actions/communicate-on-pull-request-merged/action.yml

Lines 8 to 14 in e0ddd53

	pr-comment:
	description: 'A comment to post on a pull request when code changes are merged'
	default: "Thank you for your contribution to _fastlane_ and congrats on getting this pull request merged :tada:\n
	The code change now lives in the `master` branch, however it wasn't released to [RubyGems](https://rubygems.org/gems/fastlane) yet.\n
	We usually ship about once a week, and your PR will be included in the next one.\n\n
	Please let us know if this change requires an immediate release by adding a comment here :+1:\n
	We'll notify you once we shipped a new release with your changes :rocket:"

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..."

Add GitHub Action for marking a pull request as released

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`: hide or delete the comment if the issue was edited and the information was added

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)

GitHub action that automatically adds label based on Xcode and macOS version in `env` output

Add GitHub Action for adding a comment to include `fastlane env` in an issue description

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.

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

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

Add GitHub Action for marking a PR as merged

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.

Action: Add `status: wip` do draft PRs and remove if turned into proper PR

`fastlane-env-reminder` is delivered as a container and run with docker

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

@fastlane-bot migration to GitHub Actions

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.

Add GitHub Action that automatically labels PRs by affected tool

Identify which code paths were added, automatically add labels.

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

`fastlane-env-reminder` false positives

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

`fastlane-env-reminder` runs too often on last commit on `master`

See the checks for the last commit of master:

That doesn't really look right.