GithubHelp home page GithubHelp logo

Comments (5)

peter-evans avatar peter-evans commented on June 3, 2024

Hi @glasser

Thank you for reporting this issue.

I added the add-paths feature in v3 and the stash and restore in v5. When I added those features I didn't fully consider that it would make the action a bit inconsistent in the way that it leaves git state. The stash/restore is only used when add-paths is specified. For some state like git config/auth I've made an effort to revert all changes and leave the state as it was found. I think perhaps it makes sense to try and do that consistently for all git state.

I don't really want to add additional options to the action, unless it's unavoidable. I've made an effort to keep the interface simple and not bloated with config options. So I think reverting all state in every case is simple and intuitive.

I'll take a look at this change when I get a chance. It would require a major version bump, though, because potentially it would be a breaking change for some workflows that expect a particular git state after the action completes.

from create-pull-request.

glasser avatar glasser commented on June 3, 2024

I would certainly be happy if v6 let me do the thing I wanted with zero extra configuration :)

from create-pull-request.

peter-evans avatar peter-evans commented on June 3, 2024

I remember now why the non-config git state works this way. One of the features of this action is that you can make your own commits which get included in the PR. I think it's a bit too complicated (and probably undesirable) to try and restore those commits after the action completes, so I decided to just let the git state reflect anything that wasn't committed by add-paths.

I think I would prefer to leave it the way it is for now. I might change my mind in future.

There is a pretty straightforward workaround, as an alternative to the one you are already doing. Just run the Create Pull Request for all step in a separate job in parallel.

from create-pull-request.

glasser avatar glasser commented on June 3, 2024

Makes sense. The downside to parallelizing is that constructing the file changes can be slow, so ideally that is shared across jobs. Though GH Actions does provide various ways to share state across jobs...

from create-pull-request.

peter-evans avatar peter-evans commented on June 3, 2024

Closing for now.

from create-pull-request.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.