UCL / UCL/STIR

GHA: tmate ssh access improvements

Open
#1,032 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
160
Forks
113
Avg merge
12d 15h
Merged PRs (30d)
1

Description

see https://github.com/mxschmitt/action-tmate

  • It should only be triggered for failing jobs
  • We should be able to select which job (https://github.com/mxschmitt/action-tmate/issues/121)
  • Probably should limit access to the "actor" as this facility is unsafe as the ssh sessions probably have access to secrets

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the repository's GitHub Actions workflow that invokes mxschmitt/action-tmate, then read the action documentation and upstream issue #121. The work is complete when tmate runs only for failing jobs, supports selecting a job, and restricts SSH access to the actor as far as the action permits.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.