Add some private CI when returning code to github
Open
Nobody has claimed this yet.
Component:CI
Component:OT_Blocks_Foundry
Earlgrey-PROD Triaged
Priority:P2
Type:Enhancement
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
to check it doesn't break the foundry database.
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
No files, tests, or entry points are named. Start by clarifying what “private CI” should run when code returns to GitHub and how it should check the foundry database; done means the agreed CI check runs successfully without breaking that database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100