status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
consul/.github
History
Jono Sosulska 0174b1c7c6
Add github actions for PR and issue labeling (#8709) 
* Added Issue Labeler, PR labeler, .github readme
* Updated README with Issue Template information, and regex to metrics
Co-authored-by: Kit Patella <kit@jepsen.io>
 		2020-10-05 10:43:21 -04:00
..
ISSUE_TEMPLATE Adding redirect to discuss, moving question to old (#7732) 2020-05-01 13:02:15 -04:00
workflows Add github actions for PR and issue labeling (#8709) 2020-10-05 10:43:21 -04:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-08-26 08:04:25 -07:00
README.md Add github actions for PR and issue labeling (#8709) 2020-10-05 10:43:21 -04:00
issue-labeler.yml Add github actions for PR and issue labeling (#8709) 2020-10-05 10:43:21 -04:00
pr-labeler.yml Add github actions for PR and issue labeling (#8709) 2020-10-05 10:43:21 -04:00

README.md

Consul GitHub Configuration

Overview

This file helps track the configuration of the .github/ folder.

Issue Templates

Issue templates are stored in .github/ISSUE_TEMPLATE/ and follow the documentation. The .github/ISSUE_TEMPLATE/config.yml controls links out to other support resources.

GitHub Actions

GitHub Actions provides a pluggable architecture for creating simple automation. An Action is made of at least two files, the workflow file and a config file. All workflows are stored in .github/workflows/. Configuration files are stored one directory higher, in .github/. The workflow and the configuration file should be named the same when created. Create unique and clear names for these files.

Issue Labeler

Issues are labeled with RegEx Labeler. This action supports simple regexes, and most string parsing.

PR Labeler

PRs are labeled with labeler action. This supports glob parsing so that labels can be applied to changed files.

Considered Actions

  • super-labeler-action is an action that holds all the configuration in a single file. In setting up a basic configuration with 60 labels, the JSON config became ~1200 lines. This solution may be feaseable in the future, but wouldn't seem as scaleable. This also creates a single point of failure for the entire labeling system.

  • actions-label-commenter is an action that just responds based on tags, rather than tagging them as they come in. This would be helpful for responses for reoccuring types of messages.

  • top-issues-labeler labels the top ten issues based on number of 👍 's on an inssue.