Developed action #1

Bullrich · 2023-03-31T11:49:18Z

Created GitHub action that fetches all the stale issues.

Created documentation explaining how to use it.

has full functionality and fetches the issues of a given repository

rzadp · 2023-03-31T11:53:55Z

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @paritytech/opstooling


Unknown owner on line 1: make sure the team @paritytech/opstooling exists, is publicly visible, and has write access to the repository

I think that it is failing because it was set in the other organization. Should work once merged in ours

i guess the opstooling should have admin access in this repo and it should be ok

Bullrich · 2023-03-31T11:56:40Z

.github/workflows/publish.yml

This is a copy and paste from https://github.com/paritytech/github-issue-sync/blob/master/.github/workflows/publish.yml

README.md

mordamax · 2023-03-31T12:26:54Z

few questions:

does it require all 10+ repo to duplicate the set up and a standard message? -> what would it take to slighly adjust a message in 10+ repos?
since there's an github app, which provides access to the issues, i don't fully understand why we would need a PAT if this includes private repos? afaik github app could be installed to the whole org, and have access to all repos including private, can we do it this way instead of PAT?
in the original task it states that these are "If someone from the community creates an issue there should be someone taking a look and reply." so then it provides a "lists GitHub issues without any reply that were created by non-team members.", which means that there should be a team provided too, right? which will be used in a query
updated_at is updated when someone comments the issue or adds a label?

Bullrich · 2023-03-31T12:34:45Z

does it require all 10+ repo to duplicate the set up and a standard message? -> what would it take to slighly adjust a message in 10+ repos?

No, we need one step per repo (so it can be fine tuned per repo).

In the example I added at the bottom of the readme, it handles 3 repos in the same action.

What this your action?

since there's an github app, which provides access to the issues, i don't fully understand why we would need a PAT if this includes private repos? afaik github app could be installed to the whole org, and have access to all repos including private, can we do it this way instead of PAT?

The reason for the PAT is for individual use. We can use pthe github app to generate the access token just like we do it in github-issue-sync

in the original task it states that these are "If someone from the community creates an issue there should be someone taking a look and reply." so then it provides a "lists GitHub issues without any reply that were created by non-team members.", which means that there should be a team provided too, right? which will be used in a query

I wanted to create that step in a separate commit. It also brings the question, does team refer to members of the organization?

updated_at is updated when someone comments the issue or adds a label?

Both.

Bullrich · 2023-03-31T13:00:28Z

updated_at is updated when someone comments the issue or adds a label?

@mordamax I created #2 for this.

mordamax

LGTM, but certainly needs pagination for issues query, hope we can add it right after we merge this initial

README.md

mordamax · 2023-03-31T20:38:30Z

README.md

+        uses: slackapi/slack-github-action@v1.23.0
+        with:
+          channel-id: 'CHANNEL_ID,ANOTHER_CHANNEL_ID'
+          slack-message: "Stale issues this week: \n$LOCAL_ISSUES \n$ABC_ISSUES \n$XYZ_ISSUES"


could we make an example with all our repos in https://github.com/paritytech/opstooling/tree/master/.github/workflows ?

Yes, as soon as I have a Matrix bot I'll have it running!

I can make one with no Matrix bot but that will still work in the intended way.

mordamax · 2023-03-31T20:38:55Z

README.md

+
+Stale issues this week:
+### Repo example/local has 1 stale issues
+  - [Stop AI from controlling the world](https://github.com/example/local/issues/15) - Stale for 25 days


mordamax · 2023-03-31T20:43:58Z

src/github/issuesParser.ts

+}
+
+export const fetchIssues = async (octokit: InstanceType<typeof GitHub>, daysStale: number, repo: Repo): Promise<IssueData[]> => {
+    const issues = await octokit.rest.issues.listForRepo({ ...repo, per_page: 100, state: "open" });


makes sense to add pagination
as at least this one https://github.com/paritytech/ink has > 100

may be as separate ticket would also be good to add filter by label.. so in such repos like substrate you could filter out the particular team tag

Good catch, I'll add a pagination system in a different commit

Created #4 to handle it

Co-authored-by: Maksym Hlukhovtsov <1177472+mordamax@users.noreply.github.com>

Bullrich added 8 commits March 30, 2023 18:35

created base action

7e99eb6

has full functionality and fetches the issues of a given repository

added dockerfile

34bcecb

created action.yml file

d739035

added readme

fbf6374

added ci to deploy automatically to github packages

87ffe08

updated action to use local GPR image

d354b47

added codeowners

0afe500

added multistage docker image build

c1967c5

Bullrich requested review from mutantcornholio, mordamax, rzadp and parutger March 31, 2023 11:49

Bullrich self-assigned this Mar 31, 2023

rzadp reviewed Mar 31, 2023

View reviewed changes

added development requirements

a7251f6

Bullrich requested a review from rzadp March 31, 2023 11:56

Bullrich commented Mar 31, 2023

View reviewed changes

rzadp reviewed Mar 31, 2023

View reviewed changes

README.md Outdated Show resolved Hide resolved

Bullrich added 2 commits March 31, 2023 14:05

added information on how to access other repos

4d19c8e

defaulted repo owner to organization in context

ca7f20c

Bullrich requested a review from rzadp March 31, 2023 12:08

fixed invalid readme parameters

26f5ebe

mordamax approved these changes Mar 31, 2023

View reviewed changes

Fixed old reference

a666e70

Co-authored-by: Maksym Hlukhovtsov <1177472+mordamax@users.noreply.github.com>

Bullrich mentioned this pull request Apr 1, 2023

Handle repos with more than a 100 issues #4

Closed

removed test file

27511bb

Bullrich merged commit 9e04807 into paritytech:main Apr 1, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Developed action #1

Developed action #1

Bullrich commented Mar 31, 2023

rzadp Mar 31, 2023

Bullrich Mar 31, 2023

mordamax Mar 31, 2023

Bullrich Mar 31, 2023

mordamax commented Mar 31, 2023 •

edited

Bullrich commented Mar 31, 2023 •

edited

Bullrich commented Mar 31, 2023 •

edited

mordamax left a comment

mordamax Mar 31, 2023

Bullrich Apr 1, 2023

mordamax Mar 31, 2023

mordamax Mar 31, 2023 •

edited

Bullrich Apr 1, 2023

Bullrich Apr 1, 2023

Developed action #1

Developed action #1

Conversation

Bullrich commented Mar 31, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mordamax commented Mar 31, 2023 • edited

Bullrich commented Mar 31, 2023 • edited

Bullrich commented Mar 31, 2023 • edited

mordamax left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mordamax Mar 31, 2023 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mordamax commented Mar 31, 2023 •

edited

Bullrich commented Mar 31, 2023 •

edited

Bullrich commented Mar 31, 2023 •

edited

mordamax Mar 31, 2023 •

edited