These FAQs primarily target Sandia developers working in the SandiaLabs GitHub organization. Don’t see your question listed below? Please contact SandiaLabs GitHub admins.
If you’re new to GitHub and open source in general, figuring out how to get set up can be a challenge. You may want to read through the GitHub Help pages on setting up and managing your GitHub profile.
You do not need a separate work account and personal account. Instead, you can link multiple email addresses to the same GitHub account, which is almost always preferred.
Update your profile information.
Sandia National Labs
.Add your @sandia.gov
email address (and any aliases) to your Email Settings page. This will link any commits done via your Git identity to your GitHub account.
If you are an employee at Sandia, you are eligible to join the SandiaLabs GitHub organization and appear in the member list.
Send an email, with your GitHub username included, to the SandiaLabs GitHub admins from your @sandia.gov
email, requesting to be added to the organization.
After an administrator has added you to the organization, you will receive a notification email from GitHub. Alternatively, once the invitation has been sent, you will see a notification banner at the top of github.com/sandialabs which you can use to accept the invitation.
Head over to the SandiaLabs People page and make your membership Public
.
Remember that these repositories are hosted on GitHub servers, NOT Sandia servers, and content placed in them should be limited to “email like” communications. That means:
When in doubt, contact a Derivative Classifier (DC) for further guidance.
Repositories within the SandiaLabs organization are owned and managed by Sandia. Please do not create personal repositories here.
Make sure your repository is included on this website’s home page and full catalog. If you’ve set up your repository within the SandiaLabs organization, you don’t need to take any action; it will automatically appear after the next data update.
If your repository exists under a different organization, you can move it to SandiaLabs by selecting “Transfer Ownership” under Settings.
Alternatively, you can submit a pull request updating the input_lists.json
file, with your organization and/or repository names.
If you have a project logo, please follow the instructions for naming and uploading the file. If your repo is part of a non-Sandia organization that has its own avatar, that image will automatically display next to the repo name in the catalog, unless superseded by a repo-specific logo.
Submit a pull request! This website is a GitHub repo just like any other Sandia open source project. News is housed in the _posts
directory, and templates are found in the sandialabs/.github repo. See the guidelines below about contributing.
Before contributing, please contact wg-1424-ops@sandia.gov with your idea or if you have questions about whether your proposed content requires the Sandia review and release process.
Remove your repo’s topic tags (e.g., math-physics
), which connect it to this website’s browsable categories.
Submit a pull request updating the input_lists.json
file to remove your repo’s name.
Change your repo’s status via Settings > Manage Access > Who has access > Manage > Danger Zone > Archive this repository (settings#danger-zone
). Contact wg-1424-ops@sandia.gov if for some reason GitHub won’t let you complete this step.