-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Static Sites to GSA-TTS & add build checks #4510
Comments
Blocked pending attendance of Pages Office Hours to clarify some of the security implementation details... |
Office hours scheduled for 11/2 at 11:30AM EST EDIT: We will complete a single site with Pages team and then repeat the process for the rest of the sites. |
|
setup package-ecosystem value |
@Jin-Sun-tts let's circle back together to add sdg.data.gov to this list. |
Finished all security setup/modification in https://github.com/GSA/sdg-indicators-usa except the dependabot update. Could not setup dependabot.yml file because of unsolved PR GSA/sdg-indicators-usa#1054, will check with @btylerburton on Monday. |
configuration and documentation for sdg.data.gov is done. |
checked with Ryan Wold, the feedback.usa.gov is no longer a site, and @btylerburton will work with Ryan to remove it from our https://pages.cloud.gov/sites account. |
User Story
In order to maintain our list of static sites within the GSA's Pages ATO umbrella, the Pages team would like datagovteam to migrate our static sites to the GSA-TTS org and enable a list of build checks to confirm the build is secure.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
THEN I expect to see the source repository listed under the GSA-TTS org
AND that it is managed by @GSA-TTS/data-gov-team-tts
AND that is is configured with Github Security, Security Scorecard, Github AllStar, Codeql, Dependabot and Snyk
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
Repeat the above steps for each of the following repos:
The text was updated successfully, but these errors were encountered: