tramlinehq/tramline

Attach build artifacts to the GitHub release

Open

#650 opened on Sep 18, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Ruby (32 forks)github user discovery
category / integrationshelp wanted

Repository metrics

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

Description

We should attach a copy of the final build for which the release was cut as a part of the GitHub release itself (under Assets). In this example, the user has attached the apk manually after the release was initially cut by Tramline. This can be automated.

Contributor guide

Research direction
Implement automation to upload build artifacts to GitHub release assets using the GitHub API during the release process.
Tech stack
ruby
Domain
releasedevopsbackend
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60