Describe the Use Case for the Feature:
While exploring stringy-core, I found that multiple test cases were failing due to the following mistakes:
- Exported functions multiple times.
- Not imported functions in the test files.
- Forgot to run test cases after implementing a new feature or fixing a bug.
A CI/CD setup can help us identify and address these issues, preventing them from disrupting the current workflow.
Suggested Solution:
To address all these issues, we can implement a CI/CD setup that runs test cases whenever someone raises a Pull Request. This setup will run after every commit, helping contributors quickly identify and fix any issues.
Additionally:
- We can add conditions to run
CI/CD on a draft PR by adding a label such as trigger CI/CD.
This approach ensures that the test cases are automatically executed, providing continuous feedback to contributors and maintaining the integrity of the codebase.
Describe the Use Case for the Feature:
While exploring
stringy-core, I found that multiple test cases were failing due to the following mistakes:A
CI/CDsetup can help us identify and address these issues, preventing them from disrupting the current workflow.Suggested Solution:
To address all these issues, we can implement a
CI/CDsetup that runs test cases whenever someone raises aPull Request. This setup will run after every commit, helping contributors quickly identify and fix any issues.Additionally:
CI/CDon adraft PRby adding a label such astrigger CI/CD.This approach ensures that the test cases are automatically executed, providing continuous feedback to contributors and maintaining the integrity of the codebase.