fastlane / issue-bot

This bot is responsible for commenting on GitHub issues that haven't had any activity

issue-bot

This bot interacts on GitHub issues and pull requests due to multiple reasons.

One example are issues that haven't had any activity for multiple months. Due to the fast nature of fastlane, issues often can't be reproduced anymore after 2-3 months of inactivity. Those issues are closed.

Other use cases:

• comment on PRs that were merged and will be included in the next release
• comment on PRs whose content is now available and released
• adds label to PRs that have been open for too long
• closes and locks old, inactive issues and PRs
• responds to issues that contain trigger words with specific message
• adds label to issues that require a reply from the original poster

Please note that the issue-bot system run by the fastlane core team does not automatically deploy code changes made to this repository. When merging changes to the repository, please let a member of the fastlane core team know (via Slack or at-mention in the GitHub pull request), so that they can manually deploy your code change.

Development

1. You can use rake to easily run a couple of tasks.

   Run bundle exec rake --tasks (or simply -T) to get a list of all the available tasks and their description.

   You run a task using bundle exec rake <task name>.

2. You can also use pry to test different methods from the Bot class. For example, to test the processing of new issues:

   1. cd into the repository's project
   2. run bundle exec pry
   3. execute require "logger"
   4. execute load "bot.rb"
   5. execute Fastlane::Bot.new(Logger.new(STDOUT)).start(process: :issues)

   After you modify the bot, you execute load "bot.rb" again for the new changes take effect.

3. If you want to test it with actual data, you need to create a GitHub access token by going to https://github.com/settings/tokens, generating a new token and following these steps:

   1. create a testing GitHub project
   2. update the SLUG constant with this new project's path (<username>/<project name>)
   3. run export GITHUB_API_TOKEN=<token>
   4. run the steps 2.ii - 2.v

issue-bot's Issues

lksjdf

asdlfkjasldkjf SIGNING

Needs more info about usage/installation

I'm having a problem where I don't specifically understand what to do after cloning it and compiling.

test something

Hi,

I've been using Fastlane for a bit and it's been great. However, I've had to add push to my apps and now the workflow is broken. The issue I'm having is Fastlane is not properly signing the app with the ad-hoc distribution profile I retrieved from sigh and is signing it with development.

Find way to "submit" issues, PRs and comments directly to #action in Slack

Right now one has to manually copy/paste an issue, PR or comment that requires some input to the #action channel in Slack. It would be nice if one could just include #action at the end of a message to automatically trigger this. The bot could then post a link and the text of the message.

Using fastlane's issue-bot

@KrauseFx

---

Which scopes (e.g. public_repo) do I need to use this bot for GITHUB_API_TOKEN?

Cheers,
Suriyaa Kudo

Delete @neonichu

We don't need things

A random issue

Bot didn't catch code signing issue

fastlane/fastlane#9401 should've generated the automatic code signing guide suggestion.