You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set repositories of interest and run with `triager -c /path/to/config.yaml`
6
4
7
-
This tool assists in weekly bug triages by fetching all issues and pull-requests
8
-
from repositories specified in the config file that were created (or updated)
9
-
since a pre-defined number of days (`timedelta`). These are also filtered by the `labels`
10
-
set in the config file. In case no `labels` are specified, then items that are
11
-
currently unassigned are pulled.
5
+
This tool assists in weekly bug triages and CI reports by fetching all issues, pull requests, and CI statuses from repositories specified in the configuration file. It retrieves items that were created (or updated) since a pre-defined number of days (`timedelta`). These are also filtered by the `labels` set in the config file. In case no `labels` are specified, then items that are currently unassigned are pulled.
12
6
13
7
By default, this prints out a table built from the fetched content to the console.
14
8
When run with `--send-email` it also emails this table to all the listed maintainers.
@@ -17,22 +11,185 @@ When run with `--send-email` it also emails this table to all the listed maintai
#GITHUB_TOKEN=your_github_token (optional - enter your github token here to make authenticated requests or comment this line to make unauthenticated API requests)
34
+
REPO_CONFIG = {
35
+
<organization>: {
36
+
"ci_and_bug_repos": [<listofrepositories>],
37
+
"bug_specific_repos": [<listofrepositories>]
38
+
}
39
+
}
40
+
20
41
## Usage
42
+
43
+
### Local Usage
44
+
45
+
1. Run the bug scrub:
46
+
47
+
triager --bugs -c config.yaml --log --send-email
48
+
49
+
2. Run the CI report:
50
+
51
+
triager --ci -c config.yaml --log --send-email
52
+
53
+
### Docker Usage
54
+
55
+
1. Build the Docker image:
56
+
57
+
sudo docker-compose build
58
+
59
+
2. Run the bug scrub:
60
+
61
+
sudo docker-compose run triager
62
+
63
+
3. Run the CI report:
64
+
65
+
sudo docker-compose run ci_report
66
+
67
+
### GitHub Actions
68
+
69
+
This tool uses GitHub Actions for automated reporting. To set up the workflows:
70
+
71
+
1. Store your secrets in GitHub Actions:
72
+
a) Go to your GitHub repository
73
+
b) Click on "Settings" tab
74
+
c) In the left sidebar, click on "Secrets and variables", then "Actions"
75
+
d) Click on "New repository secret"
76
+
e) Add the following secrets:
77
+
78
+
-`EMAIL_SENDER`: Your tool's email address for sending reports
79
+
-`EMAIL_PASSWORD`: Your tool's email password
80
+
-`MAINTAINERS`: A JSON string containing the maintainers' information
81
+
-`REPO_CONFIG`: A JSON string containing the repository configuration
82
+
83
+
2. The following workflows are available in `.github/workflows/`:
0 commit comments