🌱 Image build, use variables for repo push

[sjd78]

To help out people building images in a fork, use github action variables to be able to configure the target registry and image names.

Now on a fork, the destination of an image build can be set by using action variables¹:

• IMAGE_BUILD_REGISTRY (default: "quay.io/konveyor")
• IMAGE_BUILD_IMAGE_NAME (default: "tackle2-ui")

and action secrets²:

• QUAY_PUBLISH_ROBOT
• QUAY_PUBLISH_TOKEN

Footnotes

1. https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#creating-configuration-variables-for-a-repository ↩

2. https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secret ↩

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.15%. Comparing base (b654645) to head (16cf810).
Report is 232 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2090      +/-   ##
==========================================
+ Coverage   39.20%   42.15%   +2.95%     
==========================================
  Files         146      174      +28     
  Lines        4857     5577     +720     
  Branches     1164     1391     +227     
==========================================
+ Hits         1904     2351     +447     
- Misses       2939     3105     +166     
- Partials       14      121     +107     

Flag	Coverage Δ
client	42.15% <ø> (+2.95%)	⬆️
server	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.