Skip to content
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

chore: synced file(s) with cds-snc/site-reliability-engineering #45

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

sre-read-write[bot]
Copy link

@sre-read-write sre-read-write bot commented May 28, 2024

synced local file(s) with cds-snc/site-reliability-engineering.

SRE Workflow Sync

Description

Hello this is an automated PR from the Internal SRE Team.

This PR will sync some workflows that fill perform some important organizational requirements so that you don't have to.

Workflows being synced

The following is a list of workflows that are being synced by this action.

s3-backup.yml

This workflow will take shallow copy of the current state of your repo, zip that up and upload it to an s3 bucket in the SRE Tools AWS Account. This is a disaster recovery action that we are taking in the very slim chance that Github dissapears along with all of the copies of your repo on developer machines.

ossf-scorecard.yml

This workflow measures a set of security metrics and criteria designed to assess the security posture and practices of your repo and sends that information to Azure Sentinel.

export_github_data.yml

This workflow collects metadata about your repository and sends it to Azure Sentinel.

backstage-catalog-helper.yml

This workflow calls the Backstage Catalog Info Helper Action which is used to help teams get started with a basic Backstage catalog-info.yml file for their repository. This file is used to populate the Backstage Software Catalog and provides teams with the ability to keep track of key metadata related to their project.

Important Information

This PR should have zero impact on the functionality of your system and should be safe to merge without testing your application.

Please Note: You do not have to merge this PR if you wish to be exempt from this sync please contact internal sre through slack and we will remove your repo from the list of repos to sync. Be aware however that if you do this you will need to implement this functionality yourself.

Changed files
  • synced local .github/workflows/s3-backup.yml with remote tools/sre_file_sync/s3-backup.yml
  • synced local .github/workflows/export_github_data.yml with remote tools/sre_file_sync/export_github_data.yml
  • synced local .github/workflows/ossf-scorecard.yml with remote tools/sre_file_sync/ossf-scorecard.yml

This PR was created automatically by the repo-file-sync-action workflow run #9745310575

@sre-read-write sre-read-write bot added the sync label May 28, 2024
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch from 3e0b75c to 4490b2e Compare May 28, 2024 13:44
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch 15 times, most recently from 79a9810 to f97689e Compare June 5, 2024 13:40
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch 10 times, most recently from 0cd7591 to 478703e Compare June 10, 2024 13:39
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch 15 times, most recently from df78d64 to 1a83706 Compare June 25, 2024 13:44
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch 11 times, most recently from f7614e4 to 8114d68 Compare July 1, 2024 13:40
@sre-read-write sre-read-write bot force-pushed the repo-sync/site-reliability-engineering/default branch from 8114d68 to 77b5468 Compare July 1, 2024 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants