OpenFn / OpenFn/kit-lightning-integration
Add automation to publish a new action after merge to main
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 10
Description
Ensure that every time we merge to main, the next time the action runs itll use the latest version of the tests
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the repository's existing automation for merges to main and how the tests are run. Determine how a merge should publish a new action version so the next action run uses the latest tests, then verify that behavior after a merge to main.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 50/100