This is something we probably want to wait for the rebrand to occur as it could be considered "releasing". Granted these repos are already public so it wouldn't be too different than what we have now.

Hello, does anyone have an update about when the Phorge code might be hosted on GitHub? Thank you

We've created https://github.com/phorgeit and started configuring it to mirror the repos.

To keep in mind:

• disable Issues and all other features
• make a canned response to close any pull request.

As @avivey mentioned, the GitHub organization is set up. Both Aviv and I have access, and I am willing to add other people in the core team.

I have also configured it to mirror, as well as disabled issues. The only thing that is left is to test pushing (I'll keep an eye on the GH org and if pushes aren't happening then I'll generate some credentials and do some troubleshooting), and disable pull requests which may require configuring GitHub actions.

It appears there are not any public repositories yet, is this intentional?

In T15046#2761, @jeremy.norris wrote:

It appears there are not any public repositories yet, is this intentional?

Actually, what is the correct Github organization? In the description for this task, the link is to (which is where I initially looked and saw no public repositories):

https://github.com/phorgelabs

But then in the comments above, the link is to (which does appear to have public repositories that are empty?):

https://github.com/phorgeit

In T15046#2762, @jeremy.norris wrote:

Actually, what is the correct Github organization?

Fixed it. It's https://github.com/phorgeit.

If the automatic mirroring doesn't work, I guess we can manually "mirror" it for today...

@avivey I see that the repos currently access GitHub anonymously. For auto mirror to work you need to configure a valid credential. By this I mean you need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.

In T15046#2788, @MacFan4000 wrote:

@avivey I see that the repos currently access GitHub anonymously. For auto mirror to work you need to configure a valid credential. By this I mean you need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.

I was hoping that wouldn't be the case. I'll create a credential against my account, since it's currently impossible to create GitHub account keys against an orginization.

In T15046#2762, @jeremy.norris wrote:

In T15046#2761, @jeremy.norris wrote:

It appears there are not any public repositories yet, is this intentional?

Actually, what is the correct Github organization? In the description for this task, the link is to (which is where I initially looked and saw no public repositories):

https://github.com/phorgelabs

But then in the comments above, the link is to (which does appear to have public repositories that are empty?):

https://github.com/phorgeit

I don't know who owns the phorgelabs GitHub repo, and there's no public owner listed. The phorgeit orginization has both Aviv and myself, and is configured as the mirror. So the answer is phorgeit.

The labs one was me from ages ago before a GH org name was decided on. IIRC the phorge org was already claimed and I just wanted to be squatting on something that could.be used down the road. Happy to delete / change ownership / whatever else

In T15046#2789, @Matthew wrote:

need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.

I was hoping that wouldn't be the case. I'll create a credential against my account, since it's currently impossible to create GitHub account keys against an orginization.

I think they expect us to create a bot account for that. There's also an option to have an ssh key w/o and account, that is coded to a repository - they call it "deploy key".

This task is mostly done so I think it should be closed as resolved.