nmfs-ost/ghactions4r

[Feature]: make build triggers more selective

Open

#74 opened on Jun 2, 2023

View on GitHub
 (1 comment) (0 reactions) (1 assignee)R (1 fork)auto 404
good first issuerefactor

Repository metrics

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

Description

Is your feature request related to a problem? Please describe.

I noticed the build trigger for doc and style from the template runs on push to main - it could be more selective, e.g.,

on:
  # workflow_dispatch:
  push:
    paths:
      - 'R/**'
      - 'tests/**'
      - 'vignettes/**'
    branches: [main]

Describe the solution you would like.

look at the templates and modify them to be more selective

Describe alternatives you have considered

leave as is, which are simpler and easier to understand.

Additional context

No response

Contributor guide

Research direction
Review the existing GitHub Actions workflow templates (e.g., .github/workflows/*.yml) and modify the push event trigger to include 'paths' filters that limit execution to changes in directories like 'R/', 'tests/', and 'vignettes/'.
Tech stack
rgithub actions
Domain
ci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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 workflow syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80