You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@sambodeme will be your onboarding buddy and can help you if you get stuck on any of the steps in the checklist below. There's also a separate checklist that your onboarding buddy will tackle!
For you
Here's a checklist to get you started and to make sure you've got access to :all-the-things:!
If you're not already a member of BOTH the GSA and GSA-TTS GitHub organizations, follow the process outlined here, requesting access to the appropriate org(s). When it's time to send the mail, look up the Product Lead (see the staffing list) then start with this template, mailing from your GSA email address:
To: gsa-github.support@gsa.gov
Cc: [the product lead]
Subject: GSA and GSA-TTS GitHub organization membership
Body:
[Edit the following text to put in your GitHub username and your GSA email address, then remove this instruction text.]
Please add my GitHub account (https://github.com/myusername) to the following GitHub organizations:
- https://github.com/GSA
- https://github.com/GSA-TTS
I will be working on the FAC project:
- https://github.com/GSA-TTS/FAC
I have cc'd the FAC Product Lead for awareness.
Thank you!
(Note this step could take a few days; humans handle these requests.)
Note: If you're not able to do any of these yourself, you're still responsible for making sure that the right person makes them happen! (@jadudm is the backup buddy for this ticket, and can take care of any permissions-related work as needed.)
Docker compose build - I have a Mac with Apple M1 - AMD64. The 'docker compose build' cannot succeed on this. The failure message indicates that node v16 is required and also npm v9.7.1 is required.
Instructions for the issue creator:
Welcome to the team @gsa-suk!
@sambodeme will be your onboarding buddy and can help you if you get stuck on any of the steps in the checklist below. There's also a separate checklist that your onboarding buddy will tackle!
For you
Here's a checklist to get you started and to make sure you've got access to :all-the-things:!
If you're not already a member of BOTH the GSA and GSA-TTS GitHub organizations, follow the process outlined here, requesting access to the appropriate org(s). When it's time to send the mail, look up the Product Lead (see the staffing list) then start with this template, mailing from your GSA email address:
Once you are added to the GSA-TTS org, ask the person(s) with the "Maintainer" role to add you to the
FAC-team
team. This will grant you read/write access to our repositories.For engineers, also...
For your onboarding buddy
Note: If you're not able to do any of these yourself, you're still responsible for making sure that the right person makes them happen! (@jadudm is the backup buddy for this ticket, and can take care of any permissions-related work as needed.)
For engineers, also...
The text was updated successfully, but these errors were encountered: