Best practice for GitHub action

Open
#199 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing how the conformance tests are run locally and how the proposed GitHub Action would invoke them. Determine the needed start/stop command or script behavior for the development server, then verify that a workflow step can run the tests cleanly and terminate the server afterward.

Written by the indexing model from the issue text.

Description

I'm currently running the conformance tests locally, and I'd also like to add the GitHub action. The issue I'm facing is that I need to be able to cleanly start and stop my development server (within the run of the step). Is there a possible extension to the step to allow for a start/stop script or command?

Dominant language
Go
Stars
1.1k
Forks
260
Avg merge
3d 23h
Merged PRs (30d)
1

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.

More from opencontainers/distribution-spec

All issues in opencontainers/distribution-spec

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.