New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide more short way to install dotenv-linter #220
Conversation
One option is to install But it will require the user rights to |
Very nice work, thank you, unfortunately I'm a bit low on time right now. But I will have a detailed look soonish, at latest this weekend. 🚀 |
@DDtKey That's awesome! Thank you! 🔥 |
@dotenv-linter/maintainers glad to hear any comments and discuss this |
@DDtKey I've left some comments. Please, look at them. Also, please look at this example of installing via a script: https://github.com/reviewdog/reviewdog#installation. |
Also, it would be nice if we could test this script via GitHub Actions on Linux, Mac and Windows. |
Good idea, but until release 2.1.0 we cannot run a script test for Windows, because there are no published versions. |
Agree. In the first iteration we can add tests only for Mac and Linux. |
# Conflicts: # CHANGELOG.md
I made the changes we talked about, also added CI tests |
@mstruebing What do you think about it? |
# Conflicts: # CHANGELOG.md
Codecov Report
@@ Coverage Diff @@
## master #220 +/- ##
=======================================
Coverage 97.10% 97.10%
=======================================
Files 16 16
Lines 1485 1485
=======================================
Hits 1442 1442
Misses 43 43 Continue to review full report at Codecov.
|
I just resolved the conflict in But faced with an unpleasant feature, when we use api github, it has limitations on the number of calls. We need this to get the "latest" version. I see three possible solutions:
What do you think? |
In tests we could use https://github.com/dotenv-linter/dotenv-linter/releases/latest/download/dotenv-linter-os-arch.gz to always have the newest version Why do we need to print the version number on install anyway? Wouldn't it be enough to say after installation finishes we present the user the version (by using |
This approach was used before discussing the print of the installed version But in fact, I agree, this option will solve the problems of limiting api github and reduce the number of calls to |
I like this idea 👍 |
Sorry, I didn't followed the conversation :) |
@dotenv-linter/core thanks for feedback 👏 |
I thought that @mstruebing suggested getting the version of dotenv-linter using the |
This is my misunderstanding, I apologize, it option really impresses me. Thank you 👍 |
Implemented a script for more short way to install dotenv-linter (#112).
The advantage of the solution is its cross-platform.
The script is executed with
curl
/wget
and even under Windows (checked onMINGW
).Complexity is the process of automatically declaring an environment variable. In some cases, this is only possible manually at the moment.
This is a working version, I also tested on Alpine Linux.
But I would like to hear any ideas for improving or changing the approach.
Perhaps when we come to a final decision, it makes sense to create a separate repository.
Although for installing binaries with a script, it looks suitable in this repo, so far it is not more than 1 file.
✔ Checklist: