Create an Auto invite to the organization.

[sanjay-kv]

Join the Recode Hive GitHub Org by raising an [issue](you will receive an invitation on mail)
https://github.com/Recode-Hive
Let me know any further queries on this.

Refer the sample.

[sanjay-kv]

@Asymtode712 I merged all PR in this repo. can you work on this?

[Asymtode712]

@sanjay-kv Sure, please assign me

[sanjay-kv]

after this let me know any good github actions to improve overall organisation outlook I will assign those to you in level 2

[Asymtode712]

Sure, PM😉

[Asymtode712]

@sanjay-kv I'm done with the creation of the workflow and template files just wanted to remind you once you will merge this file the people who would raise the issue to join the community would get added into the organization's member list which currently you and @okaditya84 are part of, so should i proceed with the PR?

[sanjay-kv]

@Asymtode712 They won't be having merge access right? If then it's fine.

[sanjay-kv]

Small change: Currently when people open issue its opening in Stack overflow repo which can create conflicts with other issues.
So I created new repo called support.

Can the issue raise go there. If you want to create new issue under gssoc you can do that. else this issue will do.

• run failed https://github.com/Recode-Hive/Stackoverflow-Analysis/actions/runs/9148933818 @Asymtode712

[Asymtode712]

Sure, I will transfer it to support repo. No need for creating another issue

[Asymtode712]

@sanjay-kv Before that, you will have to create a PAT (Personal Access Token) and assign it to INVITE_TOKEN so that the workflow can run

[Asymtode712]

@sanjay-kv also you must create a new label by the name "invite me to the community", only then the label can be assigned to an issue while creating it

[Asymtode712]

@sanjay-kv I tested the new workflow file and came to the conclusion that even if we raise the issue in another repo 'support' it would still be reflected in our 'Stackoverflow-Analysis' repo's closed issues section

[Asymtode712]

@sanjay-kv Also my contribution which was merged earlier in this repo for this issue is also valid, you just have to do 2 things:

• Create a custom label by the name "invite me to the community".
• Create a PAT(Personal Access Token) with the permissions: admin:org, user, repo and assign it to INVITE_TOKEN as the new environment secret.

Additionally,

• If a Error: 'Resource not accessible by integration' occurs then we would have to create another PAT with permissions: repo and assign it to PERSONAL_ACCESS as new environment secret and replace instances of 'GITHUB_TOKEN' with it.

[Asymtode712]

@sanjay-kv I have explained every possibility now waiting for your final orders PM😅

[sanjay-kv]

invite me to the community

https://github.com/Recode-Hive/Support/issues/labels

This is done. +Created PAT Tokens. need to assign to env secret. will do n confirm

[sanjay-kv]

@sanjay-kv I tested the new workflow file and came to the conclusion that even if we raise the issue in another repo 'support' it would still be reflected in our 'Stackoverflow-Analysis' repo's closed issues section

That fine if it goes to closed PR

[sanjay-kv]

@sanjay-kv Also my contribution which was merged earlier in this repo for this issue is also valid, you just have to do 2 things:

• Create a custom label by the name "invite me to the community".
• Create a PAT(Personal Access Token) with the permissions: admin:org, user, repo and assign it to INVITE_TOKEN as the new environment secret.

Additionally,

• If a Error: 'Resource not accessible by integration' occurs then we would have to create another PAT with permissions: repo and assign it to PERSONAL_ACCESS as new environment secret and replace instances of 'GITHUB_TOKEN' with it.

I will fix the PAT tokens soon and update you.

[Asymtode712]

@sanjay-kv I tested the new workflow file and came to the conclusion that even if we raise the issue in another repo 'support' it would still be reflected in our 'Stackoverflow-Analysis' repo's closed issues section

That fine if it goes to closed PR

Correction: It would go to closed issues

[Asymtode712]

@sanjay-kv Also my contribution which was merged earlier in this repo for this issue is also valid, you just have to do 2 things:

• Create a custom label by the name "invite me to the community".
• Create a PAT(Personal Access Token) with the permissions: admin:org, user, repo and assign it to INVITE_TOKEN as the new environment secret.

Additionally,

• If a Error: 'Resource not accessible by integration' occurs then we would have to create another PAT with permissions: repo and assign it to PERSONAL_ACCESS as new environment secret and replace instances of 'GITHUB_TOKEN' with it.

I will fix the PAT tokens soon and update you.

Sure, take your time

[Asymtode712]

invite me to the community

https://github.com/Recode-Hive/Support/issues/labels

This is done. +Created PAT Tokens. need to assign to env secret. will do n confirm

You must create this in this particular repo as the issue would be raised from here

[Asymtode712]

@sanjay-kv I guess I have confused you a bit, let me explain you the whole scenario again and explain you have I tested the workflows:

1. Raise an issue from Stackoverflow-Analysis repo by selecting the invitation template.
2. Workflow would begin, check for the revelant label, if the label is matched it would take this issue to the Support repo and close it in Stackoverflow-Analysis repo which would be then reflected in Closed issues.
3. If the labels are not matched then the issue would remain in Stackoverflow-Analysis repo and workflow would be stopped.
4. Once the issue is transferred to Support repo's open issues, the further invitation workflow would be carried out

Now, invitation.yml template and invitation.yml workflow will still be in this repo

I guess this will help you

[Asymtode712]

@sanjay-kv Any updates??

Also, Ensure this so that you get rid of that integration error:

[sanjay-kv]

are you up for a call: I kinda confused on the workflow area.
Updated the level to level3 as you spent long time on this issue.

[Asymtode712]

@sanjay-kv sure

[sanjay-kv]

send you message on linkedin @Asymtode712

[Asymtode712]

@sanjay-kv Hope it works now🤞