-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create an Auto invite to the organization. #113
Comments
@Asymtode712 I merged all PR in this repo. can you work on this? |
@sanjay-kv Sure, please assign me |
after this let me know any good github actions to improve overall organisation outlook I will assign those to you in level 2 |
Sure, PM😉 |
@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? |
@Asymtode712 They won't be having merge access right? If then it's fine. |
Small change: Currently when people open issue its opening in Stack overflow repo which can create conflicts with other issues. Can the issue raise go there. If you want to create new issue under gssoc you can do that. else this issue will do. |
Sure, I will transfer it to support repo. No need for creating another issue |
@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 |
@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 |
@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 |
@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:
Additionally,
|
@sanjay-kv I have explained every possibility now waiting for your final orders PM😅 |
https://github.com/Recode-Hive/Support/issues/labels This is done. +Created PAT Tokens. need to assign to env secret. will do n confirm |
That fine if it goes to closed PR |
I will fix the PAT tokens soon and update you. |
Correction: It would go to closed issues |
Sure, take your time |
You must create this in this particular repo as the issue would be raised from here |
@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:
Now, invitation.yml template and invitation.yml workflow will still be in this repo I guess this will help you |
@sanjay-kv Any updates?? Also, Ensure this so that you get rid of that integration error: |
are you up for a call: I kinda confused on the workflow area. |
@sanjay-kv sure |
send you message on linkedin @Asymtode712 |
@sanjay-kv Hope it works now🤞 |
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.
The text was updated successfully, but these errors were encountered: