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
Copy file name to clipboardExpand all lines: README.md
+102-8Lines changed: 102 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,8 @@
1
-
2
-
3
1
# Ansible Network Triager
4
2
5
3
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,18 +11,118 @@ 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)
54
+
55
+
20
56
## Usage
57
+
58
+
### Local Usage
59
+
60
+
1. Run the bug scrub:
61
+
62
+
triager --bugs -c config.yaml --log --send-email
63
+
64
+
65
+
2. Run the CI report:
66
+
67
+
triager --ci -c config.yaml --log --send-email
68
+
69
+
70
+
### Docker Usage
71
+
72
+
1. Build the Docker image:
73
+
74
+
docker-compose build
75
+
76
+
77
+
2. Run the bug scrub:
78
+
79
+
docker-compose run triager --bugs -c config.yaml --log --send-email
80
+
81
+
82
+
3. Run the CI report:
83
+
84
+
docker-compose run triager --ci -c config.yaml --log --send-email
85
+
86
+
87
+
### GitHub Actions
88
+
89
+
1. Store your secrets (EMAIL_SENDER, EMAIL_PASSWORD, MAINTAINERS, GITHUB_TOKEN) in GitHub Actions secrets.
90
+
91
+
To securely store sensitive information like email passwords and recipients, we'll use GitHub Secrets:
92
+
a) Go to your GitHub repository.
93
+
b) Click on "Settings" tab.
94
+
c) In the left sidebar, click on "Secrets and variables", then "Actions".
95
+
d) Click on "New repository secret".
96
+
e) Add the following secrets:
97
+
98
+
Name: EMAIL_SENDER (Your tools email address from which you want to send emails)
99
+
Name: EMAIL_PASSWORD (Your tools email password)
100
+
MAINTAINERS: A JSON string containing the maintainers information.
#github_token: ${GITHUB_TOKEN} #Use GITHUB_TOKEN if you have a GitHub Actions workflow configured, otherwise comment this line out for unauthenticated requests."
53
-
54
-
maintainers: ${MAINTAINERS}
55
-
56
-
# github_token: 'Manually enter your github token here to make authenticated requests or comment this line to make unauthenticated API requests'
57
-
58
-
59
-
60
-
61
-
##Generic structure
62
-
# ---
63
-
# organization_name: "Organization Name" # Replace with your organization's name
64
-
65
-
# workflow_name: "workflow.yml" # Replace with your workflow file name, by default its tests.yml
66
-
67
-
# orgs:
68
-
# - name: collections-group # Name of the first group of repositories
69
-
# ci_and_bug_repos: # Repositories common between CI and bug tools
70
-
# - name: collection1
71
-
# - name: collection2
72
-
# - name: collection3
73
-
# bug_specific_repos: # Repositories only present in the bug tool
74
-
# - name: collection4
75
-
# - name: collection5
76
-
# - name: another-org # Name of the second organization or group
77
-
# bug_specific_repos: # Repositories only present in the bug tool
78
-
# - name: repo1
79
-
# - name: third-org # Name of the third organization or group
80
-
# ci_and_bug_repos: # Repositories common between CI and bug tools
0 commit comments