[Slackbuilds-users] template idea: --no-same-owner

[Lumin Etherlight]

"B. Watson" <urchlay at slackware.uk> writes:

> On Tue, 18 Aug 2026, Duncan Roe wrote:
>
>> I had the idea that I would script the PR process
>> using githup-cli  to make  the PR.  That's nearly
>> done. Then I would put it in a cron job to send a
>> constant trickle  until they  were all  done. The
>> constant trickle  is to ensure servers  don't get
>> swamped. Also gives time  to delete branches when
>> PRs are closed.
>>
>> What would you like me to do?
>
> The above looks  good: a few at a  time.  Maybe as
> many as 100 per weekly update.  I mean I've pushed
> 100  commits  in  a  week lots  of  times  without
> swamping  anything...   You   said  2777  commits,
> that'll take  28 weeks or 7  months.

        If the  git history  is inevitably  going to
  have thousands  of commits changing  little script
  compliance  things, then  I would  suggest they're
  all made in one go.  Instead of having hundreds of
  noise commits in little chunks clustered over many
  months,  we'd just  have  them all  in one  chunk,
  where someone can skip  over them when reading the
  history.  Pushing  thousands of commits in  one go
  is not an issue for git, in my experience.  Unless
  you have an expensive  automation system that will
  have to run once for each commit, of course.

Best Regards,
Lumin Etherlight