github-action | Github action for esy | Continous Integration library

Checking the Environment Variables from the Super Linter Github Action, the default value for the EDITORCONFIG_FILE_NAME file is .ecrc.

Therefore, if your file's name is .editorconfig you'll have to add it to the action arguments list with something like:

Your javascript code executes the equivalent of :

The problem seemed to be that the environment variables were not inherited when running with sudo. There are many ways to work around this, but I was able to confirm that it would run with sudo -E. Of course, if you don't need to run with sudo, you should remove it, but I guess it's necessary.

(The reproduction code was easy for me to reproduce it. Thanks)

The log shows that it tries to connect to local instance of SonarQube, not SonarCloud. You would need to configure additional parameters to connect to SonarCloud: /d:sonar.host.url=https://sonarcloud.io and /o:. See SonarCloud version of task documentation and SonarCloud required parameters.

No, you didn't miss anything in your workflows.

You just need a different token.

When you use actions/checkout, it uses the GITHUB_TOKEN for authentication, and according to the documentation it doesn't trigger a new workflow run:

When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.

To make it work, you need to generate a PAT (Personal Access Token), store it in your repository secrets, and use it in your checkout step:

You can also create workflow templates in the .github repository and share them with other users in your organization.

It definitely sounds like you should not build two different images - not for CI, and not for local development purposes (if it matters).

From the details you have provided, I would consider the following approach:

1. Define a Dockerfile with an ENTRYPOINT which is the lowest common denominator for your needs (it can be bash or python script.py).
2. In GitHub Actions, have a single job with multiple steps - one for building the image, and the others for running it with arguments.

For example:

The simple answer (from this thread) is that Heroku provides no proper way to run in a subdirectory. Any solution will be a hack, and those will vary depending on your project layout.

In my case, I got it working by putting a package.json in the root of the repo with:

The job workflow docs tell us that there's also a way of using expressions inside the url field: