community-plugins/workspaces/github-actions
Andre Wanlin 1751e05301
Various workspaces - Removed usages of `concurrently` (#2362)
Signed-off-by: Andre Wanlin <awanlin@spotify.com>
2024-12-24 14:36:48 -06:00
..
.changeset Version Packages (#2328) 2024-12-23 18:41:17 -06:00
examples add default entity filters for plugins using new FE system 2024-08-22 16:35:38 -04:00
packages github-actions - version:bump to v1.34.1 (#2302) 2024-12-23 18:21:13 -06:00
plugins Version Packages (#2328) 2024-12-23 18:41:17 -06:00
.dockerignore
.eslintignore
.eslintrc.js chore: fix workspace eslintrc files 2024-09-24 11:13:37 +02:00
.gitignore
.prettierignore
README.md Clarity in docs, keeping testing notes 2024-07-29 13:57:57 -06:00
app-config.yaml Add filtering based on annotation presence for new FE system components (#2020) 2024-11-20 08:45:09 -06:00
backstage.json github-actions - version:bump to v1.34.1 (#2302) 2024-12-23 18:21:13 -06:00
catalog-info.yaml
package.json Various workspaces - Removed usages of `concurrently` (#2362) 2024-12-24 14:36:48 -06:00
tsconfig.json
yarn.lock Various workspaces - Removed usages of `concurrently` (#2362) 2024-12-24 14:36:48 -06:00

README.md

Backstage

For testing github-actions, set the relevant env variables:

  1. Create an OAuth App in the GitHub organization with the callback URL set to http://localhost:7007/api/auth/github/handler/frame.
  2. Take the Client ID and Client Secret from the newly created app's settings page and put them into AUTH_GITHUB_CLIENT_ID and AUTH_GITHUB_CLIENT_SECRET environment variables.
  3. Generate a personal access token and put it into the GITHUB_TOKEN environment variable. You can generate a personal access token from your GitHub settings. It will need the repo and workflow scopes.

The backstage example entity has a populated github.com/project-slug annotation, but you can modify this to point anywhere your credentials have access to for testing purposes.

To start the app, run:

yarn install
yarn dev