Version 12 vs 13
Version 12 vs 13
Edits
Edits
- Edit by dereckson, Version 13
- May 15 2023 21:48
- Edit by dereckson, Version 12
- Sep 25 2022 23:19
- ·Clarification of GitHub creation process
« Previous Change | Next Change » |
Edit Older Version 12... | Edit Older Version 13... |
Content Changes
Content Changes
New repositories should be created in Phabricator and mirrored to GitHub.
Procedure depends if you can or not create a repository in Nasqueron orgz on GitHub. To do so, you must be a member of the Nasqueron orgz on GitHub, something you can ask to @dereckson
**From 2020-09-25, any new repository should use //main// instead of //master //as the reference branch.**
You have don't have access to GitHub
====================================
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/ | Create the repository ]] here
# Create a task against #DevCentral project to require to mirror it to GitHub, with a link to this document
You have access to GitHub
=========================
**DevCentral**
# [[ https://devcentral.nasqueron.org/passphrase/edit/?type=ssh-generated-key&username=git | Generate a deployment SSH key ]] to allow GitHub interaction
## **Name:** Deployment key for GitHub nasqueron/foo
## **Lock permanently:** check
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/?vcs=git | Create the repository ]]
# Add a new remote URI
## **URI:** git@github.com:nasqueron/foo.git
## **I/O type:** Mirror
## **Display type:** Default (= hidden)
# Change default branch to main (manage > branches)
# Activate the repository (manage > basics)
# Tag it with a project (Notifications center will use it to know where announce related events)
**GitHub**
# Create a new repository with `hub create nasqueron/foo` or visiting https://github.com/new
## **Privacy** : Check Public option
## **Add a README file** : Don't check the box, as the repository should be created empty. First commits should be reviewed on DevCentral too.
# Go to https://github.com/nasqueron/foo
# Add the deploy key to https://github.com/nasqueron/foo/settings/keys
## Use something like `DevCentral (K00)` where K00 is the Passphrase object as title
## Allow write access
# Consider to add the repo to a relevant team: https://github.com/orgs/nasqueron/teams
What to do afterwards?
======================
You may create and commit the following files:
| `.arcconfig` | The callsign and the DevCentral URL
| `.arclint` | Linters configuration
| `LICENSE` | When in doubt, use BSD-2-Clause
| `README` or `README.md` | Relevant pointers to get started with the repository code
Special tags
============
Those projects-as-a-tag allow to tag repositories for a specific purpose:
| #python_package | Indicate the repository is for a Python package
| #not_audited_repository | Don't trigger an audit for commits not associated to code review
New repositories should be created in Phabricator and mirrored to GitHub.
Procedure depends if you can or not create a repository in Nasqueron orgz on GitHub. To do so, you must be a member of the Nasqueron orgz on GitHub, something you can ask to @dereckson
**From 2020-09-25, any new repository should use //main// instead of //master //as the reference branch.**
You have don't have access to GitHub
====================================
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/ | Create the repository ]] here
# Create a task against #DevCentral project to require to mirror it to GitHub, with a link to this document
You have access to GitHub
=========================
**DevCentral**
# [[ https://devcentral.nasqueron.org/passphrase/edit/?type=ssh-generated-key&username=git | Generate a deployment SSH key ]] to allow GitHub interaction
## **Name:** Deployment key for GitHub nasqueron/foo
## **Lock permanently:** check
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/?vcs=git | Create the repository ]]
## **Name:** the descriptive, typography-rich repository name, e.g. Phantom and Ghosts
## **Callsign:** a short uppercase symbol, like an abbreviation, e.g. PG
## **Short name:** the name of the repository folder when you clone it, e.g. phantom-ghosts
# Add a new remote URI
## **URI:** git@github.com:nasqueron/foo.git
## **I/O type:** Mirror
## **Display type:** Default (= hidden)
# Change default branch to main (manage > branches)
# Activate the repository (manage > basics)
# Tag it with a project (Notifications center will use it to know where announce related events)
**GitHub**
# Create a new repository with `hub create nasqueron/foo` or visiting https://github.com/new
## **Privacy** : Check Public option
## **Add a README file** : Don't check the box, as the repository should be created empty. First commits should be reviewed on DevCentral too.
# Go to https://github.com/nasqueron/foo
# Add the deploy key to https://github.com/nasqueron/foo/settings/keys
## Use something like `DevCentral (K00)` where K00 is the Passphrase object as title
## Allow write access
# Consider to add the repo to a relevant team: https://github.com/orgs/nasqueron/teams
What to do afterwards?
======================
You may create and commit the following files:
| `.arcconfig` | The callsign and the DevCentral URL
| `.arclint` | Linters configuration
| `LICENSE` | When in doubt, use BSD-2-Clause
| `README` or `README.md` | Relevant pointers to get started with the repository code
Special tags
============
Those projects-as-a-tag allow to tag repositories for a specific purpose:
| #python_package | Indicate the repository is for a Python package
| #not_audited_repository | Don't trigger an audit for commits not associated to code review
New repositories should be created in Phabricator and mirrored to GitHub.
Procedure depends if you can or not create a repository in Nasqueron orgz on GitHub. To do so, you must be a member of the Nasqueron orgz on GitHub, something you can ask to @dereckson
**From 2020-09-25, any new repository should use //main// instead of //master //as the reference branch.**
You have don't have access to GitHub
====================================
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/ | Create the repository ]] here
# Create a task against #DevCentral project to require to mirror it to GitHub, with a link to this document
You have access to GitHub
=========================
**DevCentral**
# [[ https://devcentral.nasqueron.org/passphrase/edit/?type=ssh-generated-key&username=git | Generate a deployment SSH key ]] to allow GitHub interaction
## **Name:** Deployment key for GitHub nasqueron/foo
## **Lock permanently:** check
# [[ https://devcentral.nasqueron.org/diffusion/edit/form/default/?vcs=git | Create the repository ]]
## **Name:** the descriptive, typography-rich repository name, e.g. Phantom and Ghosts
## **Callsign:** a short uppercase symbol, like an abbreviation, e.g. PG
## **Short name:** the name of the repository folder when you clone it, e.g. phantom-ghosts
# Add a new remote URI
## **URI:** git@github.com:nasqueron/foo.git
## **I/O type:** Mirror
## **Display type:** Default (= hidden)
# Change default branch to main (manage > branches)
# Activate the repository (manage > basics)
# Tag it with a project (Notifications center will use it to know where announce related events)
**GitHub**
# Create a new repository with `hub create nasqueron/foo` or visiting https://github.com/new
## **Privacy** : Check Public option
## **Add a README file** : Don't check the box, as the repository should be created empty. First commits should be reviewed on DevCentral too.
# Go to https://github.com/nasqueron/foo
# Add the deploy key to https://github.com/nasqueron/foo/settings/keys
## Use something like `DevCentral (K00)` where K00 is the Passphrase object as title
## Allow write access
# Consider to add the repo to a relevant team: https://github.com/orgs/nasqueron/teams
What to do afterwards?
======================
You may create and commit the following files:
| `.arcconfig` | The callsign and the DevCentral URL
| `.arclint` | Linters configuration
| `LICENSE` | When in doubt, use BSD-2-Clause
| `README` or `README.md` | Relevant pointers to get started with the repository code
Special tags
============
Those projects-as-a-tag allow to tag repositories for a specific purpose:
| #python_package | Indicate the repository is for a Python package
| #not_audited_repository | Don't trigger an audit for commits not associated to code review
Nasqueron DevCentral · If it had been much bigger the moon would have had a core of ice. · Powered by Phabricator