💅 polishing off the tasking w/ prettify
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 23h 54m
- Merged PRs (30d)
- 29
Description
Our tasking situation here will get a lot more impressive and be less-incomplete once the changes i had proposed in https://github.com/ampproject/amp.dev/pull/3346 finally make their way over here. That is quite a high priority since it precludes the org-wide adoption of our tasking structure here. The funny thing about our currently-incomplete tasking situation here is that it is very home-grown, and although it may have already outgrown its original training wheels (the nps solution), they are still fully-functional and even still used by the CI to this day.
Contributor guide
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 proposed changes in ampproject/amp.dev#3346 and the current CI tasking references in .github/workflows/lint-and-test.yml, lines 54-94. Compare the existing home-grown tasking structure with the still-used nps setup; done should mean the incomplete tasking work is brought into the intended structure and supports org-wide adoption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100