Open lahabana opened 4 months ago
Hi. Thank you for the PR!
What OS do you use on CI? In your use cases, are scripts (shell scripts or batch files) not sufficient?
It's all github actions:
We could make it a bash script but as you can see there's no checkout so we'd end up creating the bash file and then running it. It could work or we could have a config file like I'm adding here.
In any case it's your repo if you don't feel you need the added complexity of ini files feel free to close :)
PS: another alternative I thought about was EnvVars but this was tricky for repeated args (like include/exclude
for example). Let me know if you prefer this/have a different idea.
We could make it a bash script but as you can see there's no checkout so we'd end up creating the bash file and then running it. It could work or we could have a config file like I'm adding here.
Sorry, I think I still don't understand how you want to use this feature. 😅 How do you put the .ini
file into the CI jobs?
I think we'd probably put a echo 'INI_CONTENT' > muffet.ini
Let's discuss this first in an issue! https://github.com/raviqqe/muffet/issues/365
Attention: Patch coverage is 66.66667%
with 4 lines
in your changes are missing coverage. Please review.
Project coverage is 87.60%. Comparing base (
61d5451
) to head (a948e22
). Report is 7 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
arguments.go | 75.00% | 1 Missing and 1 partial :warning: |
command.go | 50.00% | 1 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Motivation:
In CI we have multiple invocations of muffet with mostly the same arguments. This is cumbersome to maintain all the other args. Thus we'd like to have support for a config file to use as default
Implementation:
Always use
muffet.ini
. I thought it was likely unecessary to support anything different until the need comes for it.Signed-off-by: Charly Molter charly.molter@konghq.com