Skip to content

Update stefanzweifel/git-auto-commit-action action to v6 #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update stefanzweifel/git-auto-commit-action action to v6 #224

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2025 •
edited
Loading

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Type Update Change
stefanzweifel/git-auto-commit-action action major v5.0.1 -> v6.0.1

Release Notes

stefanzweifel/git-auto-commit-action (stefanzweifel/git-auto-commit-action)

v6.0.1

Compare Source

Fixed

v6.0.0

Compare Source

Added
  • Throw error early if repository is in a detached state (#​357)
Fixed
Removed
  • Remove support for create_branch, skip_checkout, skip_Fetch (#​314)

v5.2.0

Compare Source

Added
Fixed

v5.1.0

Compare Source

Changed
Fixed
Dependency Updates

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner June 10, 2025 20:32
@github-actions GitHub Actions
Copy link

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
  • If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
  • If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.

@github-actions github-actions bot added the Repo label Jun 10, 2025
@github-actions GitHub Actions
Copy link

Charts Differences:

Changes in cluster-bootstrap:



Changes in devxp-app:




Changes in devxp-dev:




Changes in devxp-infra:




Changes in tooling:




      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            


  

  
  

  
      @github-actions
  github-actions
bot

          requested a review
  from diegoluisi


    June 10, 2025 20:33    
    









      

  
        





      

  
          

  
  

  
      @renovate
  renovate
bot

        force-pushed
    the
        
      
  renovate/stefanzweifel-git-auto-commit-action-6.x


    
 branch
    from
    16ff246    to
    f0cf2dc      
    Compare
  



    June 11, 2025 17:16    
    









      

  
      



  

  @github-actions

    
      GitHub Actions
    




  



    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

  





      


        



  
    

      
          
Review Checklist


Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.


General


    

  •  Ensure that the Pull Request has a descriptive title.
    • 

  •  If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
    • 

  •  If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
    • 

  •  If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.
    • 



Bug fixes


    

  •  There should be at least one unit or end-to-end test.
    • 

  •  The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.
    • 



Non-trivial changes


    

  •  There should be some code comments as to why things are implemented the way they are.
    • 



New/Existing features


    

  •  Should be documented, either by modifying the existing documentation or creating new documentation.
    • 

  •  New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.
    • 



Backward compatibility


    

  •  Protobuf changes should be wire-compatible.
    • 

  •  Changes to _vt tables and RPCs need to be backward compatible.
    • 

  •  vtctl command output order should be stable and awk-able.
    • 


      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    
















  
  

    

      

  




      


    


    

      

        
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



      

    

  




  
          



      

  

    
    

    

  

    Reviewers
  


    


      

          


  
      @diegoluisi
  
    diegoluisi


                Awaiting requested review from diegoluisi


        
      


      






    

  


      
  

    Assignees
  



        


      

        


  
      @diegoluisi
  
    diegoluisi
    

      








      


  


  

    Labels
  



    

      

    dependencies

  

    Repo









      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
      

  

    

      1 participant
    

    

        
          @diegoluisi