OpenFreeEnergy / OpenFreeEnergy/openfe
To re-render or not to re-render?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 331
- Forks
- 56
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 13
Description
In our feedstock building test, I am not sure if we should include a step where we re-render the feedstock. I think we should, since if we want to reduce surprises on release day, we should. Re-rendering updates the global pins, so it would help us identify an issue with upstream dependencies.
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
Locate the feedstock building test and inspect how it currently handles rendering and global pins. Decide whether a re-render belongs in that test, then ensure the test reflects the decision and can expose upstream dependency changes before release.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100