Compare commits

...

7 Commits

Author SHA1 Message Date
Trabelsi Tobias
7295e71c95 REL-2179 update base image 2022-02-22 15:09:40 +01:00
Pierre Guillot
b755ad2c7e Merge pull request #20 from SonarSource/fix/re-bot/ownership
fix(BUILD-1287): repository ownership
2022-02-03 08:26:30 +01:00
Julien Carsique
7153604e5b fix(BUILD-1287): add repository owner 2022-02-02 18:58:14 +01:00
Tobias Trabelsi
1f3c95ed10 Docker-10 document locales and remove ANSI locale to use the one from the parent image 2021-09-24 08:03:04 +02:00
belen-pruvost-sonarsource
495aa71ae8 Merge pull request #12 from SonarSource/lj/feature/updating-contributing-md
Updating contributing md
2021-06-25 14:53:44 +02:00
Lukasz Jarocki
a81ac001b5 Updating contributing md 2021-06-25 10:55:16 +02:00
Wouter Admiraal
9b49068b67 Make it more explicit that we do not look for external contributions 2021-06-17 15:15:29 +02:00
5 changed files with 52 additions and 5 deletions

1
.github/CODEOWNERS vendored Normal file
View File

@@ -0,0 +1 @@
* @sonarsource/sonarqube-team

12
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View File

@@ -0,0 +1,12 @@
Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes. If you would like to see a new feature, please create a new thread in the forum ["Suggest new features"](https://community.sonarsource.com/c/suggestions/features).
With that in mind, if you would like to submit a code contribution, make sure that you adhere to the following guidelines and all tests are passing:
- [ ] Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
- [ ] Make sure any code you changed is covered by tests
- [ ] If there is a [JIRA](http://jira.sonarsource.com/browse/SONAR) ticket available, please make your commits and pull request start with the ticket ID (SONAR-XXXX)
We will try to give you feedback on your contribution as quickly as possible.
Thank You!
The SonarSource Team

View File

@@ -1,6 +1,6 @@
FROM sonarsource/sonar-scanner-cli:4.6 FROM sonarsource/sonar-scanner-cli:4.7
LABEL version="1.0.0" \ LABEL version="1.1.0" \
repository="https://github.com/sonarsource/sonarqube-scan-action" \ repository="https://github.com/sonarsource/sonarqube-scan-action" \
homepage="https://github.com/sonarsource/sonarqube-scan-action" \ homepage="https://github.com/sonarsource/sonarqube-scan-action" \
maintainer="SonarSource" \ maintainer="SonarSource" \
@@ -9,9 +9,6 @@ LABEL version="1.0.0" \
com.github.actions.icon="check" \ com.github.actions.icon="check" \
com.github.actions.color="green" com.github.actions.color="green"
# Set up local envs in order to allow for special chars (non-asci) in filenames.
ENV LC_ALL="C.UTF-8"
# https://help.github.com/en/actions/creating-actions/dockerfile-support-for-github-actions#user # https://help.github.com/en/actions/creating-actions/dockerfile-support-for-github-actions#user
USER root USER root

View File

@@ -52,6 +52,17 @@ jobs:
SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }} SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }}
``` ```
If your source code file names contain special characters that are not covered by the locale range of `en_US.UTF-8`, you can configure your desired locale like this:
```yaml
- name: SonarQube Scan
uses: sonarsource/sonarqube-scan-action@master
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }}
LC_ALL: "ru_RU.UTF-8"
```
You can change the analysis base directory by using the optional input `projectBaseDir` like this: You can change the analysis base directory by using the optional input `projectBaseDir` like this:
```yaml ```yaml

26
contributing.md Normal file
View File

@@ -0,0 +1,26 @@
Contributing
============
If you would like to see a new feature, please create a new thread in the forum ["Suggest new features"](https://community.sonarsource.com/c/suggestions/features).
Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes.
## Submitting a pull request
With that in mind, if you would like to submit a code contribution, please create a pull request for this repository. Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make.
Make sure that you follow our [code style](https://github.com/SonarSource/sonar-developer-toolset#code-style) and all tests are passing (Travis build is executed for each pull request).
## Next steps
One of the members of our team will carefully review your pull request. You might be asked at this point for clarifications or your pull request might be rejected if we decide that it doesn't fit our roadmap and vision for the product.
If your contribution looks promising then either we will decide:
- it is good to go and merge your pull request to the master branch
or
- that we need to think over your change and modify it to adhere to our roadmap and internal standards. We will close your pull request at this point, but we might come back to your changes later in the future when we decide it is the right time to work on it.
Thank You!
The SonarSource Team