bee-san/RustScan

Automatically upload artefacts to latest release

Open

#700 opened on Nov 25, 2024

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Rust (19,268 stars) (1,284 forks)batch import
good first issue

Description

https://github.com/RustScan/RustScan/blob/master/.github/workflows/build.yml

Our CD here creates artefacts, but does not upload them automatically.

We'd like these to be uploaded to the latest releasel.

To Do

  1. Change workflow to run on release published
  2. Upload all artefacts to the latest release. There are some ways to do this, feel free to explore!

Testing

I would test this in a local repo first, just use cargo init to make a new cargo project and test away :)

Contributor guide

Tech stack
rustgithub actions
Domain
devopsci cdrelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub ActionsYAMLRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue is about modifying the existing build.yml workflow file at .github/workflows/build.yml. The main tasks are to change the workflow trigger to 'release: published' and then add a step to upload the generated artifacts to the corresponding release. You can explore GitHub Actions like 'actions/upload release asset' or use the GitHub CLI. Test the changes in a local repository by creating a dummy Rust project and simulating a release. Check the existing workflow for artifact generation steps and ensure the upload step runs after them.