You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
Right now any workflow development gets tested just manual and happens on a best-effort basis
This is not ideal and costs lots of time.
This process should be automated while using e.g. the reset_test_repo workflow as a baseline to test other workflows.
How would you imagine the implementation of the feature?
For every test the testing repo should get reset, prepared to provide any data required and run a workflow.
Afterwards another workflow should check the resulting stet of the repo to verify if all changes got apllied as expected.
Test for tags beeing on actual release commit
There might also be streamlining possibilities which willr euqire some RnD
Are there any labels you wish to add?
I have added the relevant labels to the feature request.
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Right now any workflow development gets tested just manual and happens on a best-effort basis
This is not ideal and costs lots of time.
This process should be automated while using e.g. the reset_test_repo workflow as a baseline to test other workflows.
How would you imagine the implementation of the feature?
For every test the testing repo should get reset, prepared to provide any data required and run a workflow.
Afterwards another workflow should check the resulting stet of the repo to verify if all changes got apllied as expected.
There might also be streamlining possibilities which willr euqire some RnD
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: