Skip to content

Should this repo be public #23

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.

Sign up for GitHub

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

Jump to bottom
Open
lukehinds opened this issue Mar 5, 2025 · 3 comments
Open

Should this repo be public #23

lukehinds opened this issue Mar 5, 2025 · 3 comments
Assignees
@ChrisJBurns

Comments

@lukehinds
Copy link

I made the repo public, because I was lazy and did not want to login to my github account on a VM. We should likely be private, until we know what we are doing.
@lukehinds
Copy link
Author

@ChrisJBurns , I figure we can make this private, I only had it public for cloning to a GCP machine?

@ChrisJBurns
Copy link
Contributor

@lukehinds Yeah we should be able to, I'd need some creds to give the EC2 to be able to pull it though. Not sure if we have a dedicated bot account for this or if we wanted to create a simple GH App?

@ChrisJBurns
Copy link
Contributor

@lukehinds Do we need this anymore?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChrisJBurns ChrisJBurns

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukehinds @ChrisJBurns