NASA-AMMOS / NASA-AMMOS/AIT-GUI
Move build to GitHub actions
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 15
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
See Core ticket for info on how this was implemented there.
NASA-AMMOS/AIT-Core#467
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 reviewing the referenced NASA-AMMOS/AIT-Core#467 ticket, which contains the implementation details for this build migration. Identify the corresponding build entry points in AIT-GUI and compare them with the Core ticket; done means the project build runs through GitHub Actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100