[Slackbuilds-users] GitHub PR and update to an update

[Jay Lanagan]

 I just did this today with python3-aiohttp. If you did a PR for the previous update, just do another commit to that branch, and it will carry that forward as the latest revision which would then be the one merged into master this week.*
  

  
* provided it passes all the checks and tests.   
  
  
  
— Jay Lanagan
  
  
  

  
  
>   
> On Oct 30, 2025 at 6:14 PM,  <Andrzej Telszewski (mailto:andrzej at telszewski.com)>  wrote:
>   
>   
>     
> Hi,
>   
>   I've sent an update for *qbs* using GitHub PR.
>   Now, newer version of qbs is available, and I'd like to sent this update as well.
>   
>   However, I cannot target master, because the previous update is not there yet.
>   
>   How can I achieve that using GH PR?
>   Should I target some other branch possibly?
>   
>   Thanks!
>   
>   
>  --
>   Best regards,
>   Andrzej Telszewski
>  _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/            
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20251030/3a161ed2/attachment-0001.htm>