@nicodecleyre thank you for this suggestion based on our discussion.
In the initial conversation we were even thinking of combining it with increment version number and deploy.
What do we go even few steps further?
So except adding the gulp publish task we would also add a new action which will be increment + publish + deploy?

As for the question I don't have any hard opinion on that. If you think having a single task with a prompt instead of two separate tasks then I say we may roll with this idea 👍.
Till now we had separated tasks for local and production bundles/packing so that it is easier to find but I agree the list gets longer and longer. Maybe it does make sense to refactor them to a single task w with a prompt question which should be done local or production and default should be local 🤔

hmm, i don't know if we should hard define the increment step in this publish task. As maybe the user opted to change the version number manually. I'm more of a fan of creating a setting as discussed in the other issue, and only if this setting is checked, then the increment prompt should show up in the bundle & publish task. What do you think?

Indeed, as the list gets longer it's best to keep it as clear as possible; i will create a seperate issue to change the bundle & package solution tasks into one for each

Indeed, as the list gets longer it's best to keep it as clear as possible; i will create a seperate issue to change the bundle & package solution tasks into one for each

yes lets do that

hmm, i don't know if we should hard define the increment step in this publish task. As maybe the user opted to change the version number manually. I'm more of a fan of creating a setting as discussed in the other issue, and only if this setting is checked, then the increment prompt should show up in the bundle & publish task. What do you think?

Sorry maybe I wasn't clear. My idea was not to add increment step to publish but create something additional as well.
So the first thing we could add is a new Task with name publish and which will combine bundle & package like described in this issue 👍

Additionally I was thinking to add a new Action, I don't have a new name for it yet, but the idea would be it would combine increment + publish (bundle & package) + deploy. This could also be a separate issue and discussion. What do you think?

hmm, i don't know if we should hard define the increment step in this publish task. As maybe the user opted to change the version number manually. I'm more of a fan of creating a setting as discussed in the other issue, and only if this setting is checked, then the increment prompt should show up in the bundle & publish task. What do you think?

Sorry maybe I wasn't clear. My idea was not to add increment step to publish but create something additional as well. So the first thing we could add is a new Task with name publish and which will combine bundle & package like described in this issue 👍

Additionally I was thinking to add a new Action, I don't have a new name for it yet, but the idea would be it would combine increment + publish (bundle & package) + deploy. This could also be a separate issue and discussion. What do you think?

Ah, now i get it! Yes, this new action can be a real timesaver! As for a name maybe something like "Deploy all" or "Ship"?

"Ship it 🚢"
I like that one 😂👍

Ok this issue -with the publish task is clear.
Thanks @nicodecleyre for the awesome discussion and wrapping it up.
Let's open this up. would you like to take it?

Ok this issue -with the publish task is clear. Thanks @nicodecleyre for the awesome discussion and wrapping it up. Let's open this up. would you like to take it?

It's a good first issue, let's see if someone from the community is interested in taking this one 🙏