-
Notifications
You must be signed in to change notification settings - Fork 4
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
Private Only Tasks #20
Comments
Perhaps we need some github env variable like |
/start |
@okhot the deadline is at 2024-03-25T16:57:41.799Z |
@pavlovcik To ensure this is working correctly I have to Auth as a core member. Please how can I archive that as I presently don't know how to do so. |
https://github.com/ubiquity/devpool-directory-private/blob/development/opt.json already contains only private repositories, I don't understand what additional checks should be implemented
I think this quick fix is already removed (I remember there was some check for organization name) but I couldn't find the exact commit |
@rndquu then there's no need for this issue to exist then? |
/stop |
+ You have been unassigned from the task |
This issue may be closed as "not planned" because:
Overall it makes sense to setup code sync between |
https://github.com/ubiquity/devpool-directory-private is our new "backend" to read private issues and populate them on the devpool.directory
This should ONLY populate with private repository issues. This is so we don't have redundant data on the public and private directories.
Also re-enable "referencing" back to private repository issues (I just disabled it entirely in that repo as a quick fix by disabling the logic if its not the public devpool-directory repo https://github.com/ubiquity/devpool-directory-private/blob/development/helpers/github.ts#L63.) This means that the bot should paste in the normal URL in the GitHub comment so that the mirrored issue is "referenced" in the real issue conversation.
Ensure that this works as expected by testing the UI on the devpool.directory (you must auth as a core team member)
The text was updated successfully, but these errors were encountered: