Le dim. 5 janv. 2025 à 15:49, Elliotte Rusty Harold
a écrit :
>
> I do think the mailing list is severely misconfigured if it's paying
> any attention to dev branches. There's no reason it should be picking
> these commits up. If it is, let's fix it, not contort people's
> development processes an
On Sun, 5 Jan 2025 at 20:29, Benjamin Marwell wrote:
>
> +1, works well in other projects as well, and if needed, we can always
> extend on that.
> Questions should go to SO (or, maybe, to discussions).
SO can be the next step, now we have a ML.
I would like to enable GitHub Issues for some of t
Maintaining a custom ruleset is quite a bit of work.
And sometimes we could miss something by a disabled option...
But I think we could make a PR fail only if new severe issues are
introduced, ignoring the others (i.e. warn is informational)
By the way, there are 100s more rules, e.g. no dot-chain
On Sun, Jan 5, 2025 at 7:28 PM Benjamin Marwell wrote:
>
> Not sure about Elliotes NPEs. The ones I checked were valid, e.g.:
> https://sonarcloud.io/project/issues?open=AZQn8ht1KAwsFelognsS&id=support-and-care_maven
>
That does look like a real bug, better than any of the ones I
initially notice
Absolutely! This was only about palantir, the java formatter.
Spotless (the plugin running palantir) can also do XML etc., so we can
keep that! :)
At work, I have the format goal in validate or initialize phase or so,
the CI runs `mvn spotless:check` before running `mvn verify` -- this
way, clean
+1, works well in other projects as well, and if needed, we can always
extend on that.
Questions should go to SO (or, maybe, to discussions).
Am Sa., 4. Jan. 2025 um 22:37 Uhr schrieb Slawomir Jaranowski
:
>
> On Sat, 4 Jan 2025 at 22:28, Matthias Bünger
> wrote:
> >
> > Hi,
> > I personally don
Not sure about Elliotes NPEs. The ones I checked were valid, e.g.:
https://sonarcloud.io/project/issues?open=AZQn8ht1KAwsFelognsS&id=support-and-care_maven
And even when calling another method inbetween, the explanation is excellent:
https://sonarcloud.io/project/issues?issueStatuses=OPEN%2CCONFIR
I do think the mailing list is severely misconfigured if it's paying
any attention to dev branches. There's no reason it should be picking
these commits up. If it is, let's fix it, not contort people's
development processes and put still more restrictions and constraints
on the already very limited
The link is more than three years old. One of the replies from SonarQube
contains a link that states that it is meanwhile (Aug 24) possible for projects
configured for Automatic Analysis
(https://portal.productboard.com/sonarsource/1-sonarqube-cloud/c/50-sonarcloud-analyzes-external-pull-request
https://community.sonarsource.com/t/code-analysis-on-pull-request-from-forked-repository-with-github-actions/43986
On Sun, 5 Jan 2025 at 02:58, Gerd Aschemann wrote:
>
>
>
> > On 4. Jan 2025, at 22:28, Slawomir Jaranowski
> > wrote:
> >
> > On Thu, 2 Jan 2025 at 14:10, Konrad Windszus wrote:
>
10 matches
Mail list logo
