2nd draft for Registering an Image

[TDDR]

Issue This PR Addresses

Fixes #1743

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

This is my second draft of this after attempting to use a different workflow in a previous iteration. I have tried multiple different ways to try and get the buider to go into a sub directory instead of using the Dockerfile in the root with varying results

I think the version in this PR is the proper way to go about it, but it's not supported yet

I could be wrong but I'm not sure what else to try.

[gitpod-io]

[cindyorangis]

I'm very interested in this GitHub Container Registry stuff. Were you able to push an image from your personal issue-1743 branch?

[TDDR]

Not yet, but having that allows the workflow to trigger when I push it to my fork for testing purposes.

[TDDR]

A couple if the iterations went through the entire process but failed on the final push, but it was using the wrong Dokerfile anyway. I figure if I can get it to do this on the proper file then when I switch that to master and merge it it should work

[humphd]

This is looking great. One more thing I notice.

[humphd]

Let's try this and see what it does.

NOTE: we'll need to make a change within src/api/feed-discovery/** for this to do anything once it lands. Maybe update one of the deps?

[humphd]

@TDDR can you squash, rebase, and reword this?

git checkout master
git pull upstream master
git checkout issue-1743
git rebase -i master
...change first commit to reword, second to fixup, save, then rewrite commit message, save again
git push origin issue-1743 -f