sandstorm-io/vagrant-spk

Implement GitHub Actions for releases

Open

#256 opened on Feb 3, 2020

View on GitHub
 (8 comments) (1 reaction) (1 assignee)Python (28 forks)github user discovery
good-first-issuehelp wantedrelease-distrib

Repository metrics

Stars
 (58 stars)
PR merge metrics
 (PR metrics pending)

Description

Since we need to install things like WINE and github-release and such to do vagrant-spk releases, and most of the release process is already well-scripted, we should consider making this a GitHub Action.

Currently this repo fails to document or include installation of the github-release tool the release script depends on. Kenton knows the github-release tool he used for the last release is version 0.7.2, and I found https://github.com/aktau/github-release/releases/tag/v0.7.2 which I believe is plausibly the correct one.

Contributor guide

Research direction
Set up a GitHub Actions workflow that installs WINE and the github release tool, then runs the release script.
Tech stack
pythonshell
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.
1-2 days
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
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50