Ability to edit an existing release instead of uploading new

[chrismclarke]

Would it be possible to add the ability to edit an existing release via action instead of uploading? I'm wondering if this might be as simple as running the script without a release file (removing the required field)?

A use case for this would be workflows where the action on one github branch submits a release to internal testing, and then another branch/release could be used to promote the same release to beta or production tracks.

(found this stackoverflow article which seems to think it's possible https://stackoverflow.com/questions/49588393/promoting-beta-apk-to-production-programmatically)

[r0adkll]

That definitely seems feasible per the docs: https://developers.google.com/android-publisher/tracks, where I can update a release and specify a track to move it to. I will look into implementing this.

[boswelja]

I think things like changing status from inProgress to completed or halted could be separate actions, since this action is targeted at uploading APK/AAB to Google Play. It shouldn't be too difficult to allow passing in an Edit ID for uploading new builds to an existing edit, and we can totally expose the edit ID as an output field. Any thoughts @chrismclarke ?

[boswelja]

fwiw I do already have an action to promote open testing to production here: https://github.com/boswelja/promote-play-beta-action
It doesn't have much flexibility right now, but if it's something people are interested in I can make some changes to accommodate more configurations :)

[chrismclarke]

I think splitting the functionality for uploading new release to a track vs promoting from one track to another makes a lot of sense to me, I think the action you've created sounds near ideal (guessing would just need to expose options for source and target tracks instead of hardcoded beta/production).

For now I've found ways around this on the projects I needed it for, but good to know that's an option - thanks for letting me know about it @boswelja.

[boswelja]

Perfect, I'll look into passing an existing edit ID in to this action + exposing tracks for promotion in my other action. Thanks for your input!

[boswelja]

As of #120 we can pass in an edit ID to avoid creating a new edit every time. Still a few things needed before we can truly edit existing edits, namely

• Outputting the edit ID
• Add an option to prevent publishing edits

[abhi250401]

where can i get this edit ID ?

[petros-chariskos]

Some action here is more than welcome!

[boswelja]

where can i get this edit ID ?

From anywhere that outputs it (you can also make the API calls yourself). I'm not sure what else to say?

Some action here is more than welcome!

You are welcome to open a pull request 😄

To reiterate, we still need

• A means of preventing edit commits
• A means of outputting the edit ID, when the edit was not committed