Hi Robert,
Thanks a lot for driving this and having the guts to modify hundreds of repos.
Much appreciated.
Konrad
> On 7. Aug 2025, at 12:07, Robert Munteanu wrote:
>
> On Wed, 2025-07-23 at 18:53 +0300, Robert Munteanu wrote:
>> I filed https://issues.apache.org/jira/browse/SLING-12866 to tr
On Wed, 2025-07-23 at 18:53 +0300, Robert Munteanu wrote:
> I filed https://issues.apache.org/jira/browse/SLING-12866 to track
> this. Does anyone have any mass changes planned we should include?
The changes have been pushed yesterday, the master branch is protected
now by default via .asf.yaml .
Thanks for the input. Removing the protection is it straightforward and doesn’t
require ASF INFRA involvement. You just temporarily change the asf.yaml again
(as outlined in
https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branchpro).
Meanwhile the GitHub branch protection is
On Wed, 2025-04-30 at 11:51 -0700, Eric Norman wrote:
> Also, we may need to think of the process to handle the exceptions to
> that
> rule if a force push is temporarily necessary for some special case.
That is a good point. I think the the only way out is to ask ASF Infra
to remove branch protec
On Wed, 2025-04-30 at 15:31 +0200, Konrad Windszus wrote:
> WDYT about adding this to all our .asf.yaml’s?
+1
Robert
On Fri, 2025-05-02 at 10:00 +, Stefan Seifert wrote:
> not sure if we have modules where the default branch is not called
> master.
I strongly doubt it, the repo scripts would break otherwise.
Robert
-Original Message-
> From: Konrad Windszus
> Sent: Wednesday, April 30, 2025 3:31 PM
> To: dev@sling.apache.org
> Subject: Disable force push on default branch
>
> Hi,
> It seems that a git force push on the main branch is not disabled by
> default for the Apache repositorie
+1 from me. Eric raises a valid issue rgd. a process around it in case
due to security reasons. Presumably, we could change the .asf.yaml
file (temporarily) should a situation arise that requires a force
push?
Regards
Julian
On Wed, 30 Apr 2025 at 20:52, Eric Norman wrote:
>
> I don't think I ha
I don't think I have ever done a force push on purpose so I had to refresh
my memory on what the implications were for such things.
I found a summary snippet at
https://github.com/orgs/eclipse-csi/discussions/7 that clarified the risks
in my mind so maybe that info is helpful for others?
Force-pu
Hi,
It seems that a git force push on the main branch is not disabled by default
for the Apache repositories.
However I would strongly suggest to enforce this.
This seems to require a dedicated item within the .asf.yaml for each repository
(https://github.com/apache/infrastructure-asfyaml?tab=re
10 matches
Mail list logo
