Skip to content

Automatically run tests#1

Open
eddy-ccc wants to merge 2 commits into
mainfrom
tests_workflow_action
Open

Automatically run tests#1
eddy-ccc wants to merge 2 commits into
mainfrom
tests_workflow_action

Conversation

@eddy-ccc

@eddy-ccc eddy-ccc commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator
  • Add GitHub workflows file to run R CMD check

@hullingsag hullingsag left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Demoing Unit Tests - Approving these changes

@KELSEYDOWLING7 KELSEYDOWLING7 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eddy-ccc Is the github secret token needed here? Our other YAMLs don't have it. Not sure if this is just an additional precautionary step or necessary for the force check before merging to main

@eddy-ccc

eddy-ccc commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator Author

@KELSEYDOWLING7 Great question! This is unique to GitHub... secrets is an object provided to us by GitHub Actions itself that we can reference within the yaml. The GITHUB_TOKEN is an attribute of that object, which is created for us by GitHub, and allows the repo to authenticate with the GitHub API during the testing workflow, without us having to create or manage a personal access token. GitHub automatically mints it at the start of the run and revokes it when the job ends.

@KELSEYDOWLING7

Copy link
Copy Markdown

@eddy-ccc Ah! Ok perfect. That was moreso my question, whether we'd have to create and maintain the token. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants