Skip to content

Conversation

@kkarhan
Copy link

@kkarhan kkarhan commented May 6, 2023

based off the Commander X16 Videos by David "8-Bit Guy" Guy...

based off the Commander X16 Videos by David "8-Bit Guy" Guy...
@indigodarkwolf
Copy link
Collaborator

Hi @kkarhan,
Earlier this year, the X16 community forked from CommanderX16 and created Commander X16 Community. This is where we have been continuing to update and develop documentation and software related to the Commander X16.

I do have the power to pull this change, but our community maintainers decided at the time that it would be best not to pull new changes into CommanderX16 in the event that we should merge back at a later date -- it would be much easier to do so with fewer PRs creating potential conflicts from the point where we forked.

Please feel welcome to join us at the new repo, and I apologize for the confusion this may have caused.

@kkarhan
Copy link
Author

kkarhan commented May 7, 2023

Thanks for your quick response, @indigodarkwolf.

To avoid you and others from repeating this everytime, I'd suggest to add this on the README.md and the Issues and Pull Request drafts so that everyone gets to see this.

And whilst it's kinda uncommon [most orgs will just use branches to seperate "main" from "dev" or "testing"] it's good to know.

@kkarhan
Copy link
Author

kkarhan commented May 7, 2023

@indigodarkwolf as per your suggestion, I've made a pull request on said repo.
X16Community/x16-docs#30

I'll keep this PR open for maintainers to make a decision.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants