Deployment preview workflow

[shubhusion]

Summary of Changes

Created a new yml file and updated workflow

Related Issue

Closes #91

Checklist

• I have read and followed the project's contribution guidelines, including code style and commit message conventions.
• My code is well-documented, and I've updated relevant documentation.
• I have added or updated test cases to ensure the code's functionality.
• I have tested these changes on my local environment.
• All tests pass, and there are no new linting errors.
• I have reviewed and proofread my code and the changes.
• The branch is up-to-date with the base branch.

Screenshots (if applicable)

Attach any screenshots or images related to the changes.

Additional Context

Add any additional context or information that might be helpful for reviewers.

Reviewer(s)

@Abhijay007 @jhdalek55

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ Reference build (Review)	1 changed	May 28, 2024, 9:57 AM

[shubhusion]

It seems Github-action-bot do not have access to make changes in the repo. I am getting an error in that line.

[Abhijay007]

It seems Github-action-bot do not have access to make changes in the repo. I am getting an error in that line.

Seems like a permission error, maybe need to config a new GitHub token, cc: @hexsecs, @tkfu

[shubhusion]

@hexsecs please review this PR

[hexsecs]

We need to investigate how to make this secure. We don't want to allow anyone to arbitrarily publish to the uptane.org domain by issuing a pull request.

[hexsecs]

We need to investigate how to make this secure. We don't want to allow anyone to arbitrarily publish to the uptane.org domain by issuing a pull request.

[tkfu]

I missed this one when it first came around. The security part can be solved by a setting in the repository permissions @hexsecs :

We already have it set so that a PR from a first-time contributor won't automatically trigger any workflows; we can potentially tighten it up more so that it requires manual approval to run all workflows for external contributors. I think I'm ok with the risk profile of our current setting.

[tkfu]

Github posted a blog about this a couple years ago when they introduced the feature: https://github.blog/open-source/maintainers/github-actions-update-helping-maintainers-combat-bad-actors/