ed0156311a
* clean-up: remove false positives from knip reports Signed-off-by: Kashish Mittal <kmittal@redhat.com> * yarn dedupe Signed-off-by: Kashish Mittal <kmittal@redhat.com> * fix tests Signed-off-by: Kashish Mittal <kmittal@redhat.com> * fix failing tests Signed-off-by: Kashish Mittal <kmittal@redhat.com> * yarn dedupe Signed-off-by: Kashish Mittal <kmittal@redhat.com> --------- Signed-off-by: Kashish Mittal <kmittal@redhat.com> |
||
|---|---|---|
| .. | ||
| .changeset | ||
| examples | ||
| packages | ||
| plugins | ||
| .dockerignore | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| README.md | ||
| app-config.yaml | ||
| backstage.json | ||
| catalog-info.yaml | ||
| package.json | ||
| tsconfig.json | ||
| yarn.lock | ||
README.md
Backstage
This is your newly scaffolded Backstage App, Good Luck!
For testing sonarqube, set the relevant env variables:
- Create an OAuth App in the GitHub organization with the callback URL set to
http://localhost:7007/api/auth/github/handler/frame. - Take the Client ID and Client Secret from the newly created app's settings page and put them into
AUTH_GITHUB_CLIENT_IDandAUTH_GITHUB_CLIENT_SECRETenvironment variables. - Generate a personal access token and put it into the
GITHUB_TOKENenviornment 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 sonarqube.org/project-key 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