Giters

ncipollo / release-action

An action which manages a github release

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Release created via this action gets drafted if a git branch is updated

seppzer0 opened this issue · comments

commented

Describe the bug
After I've released a tag via this action, if I push any update on any of the branches of the repository, the release get automatically drafted, which should not happen.

To Reproduce
Steps to reproduce the behavior:

  1. Create a release using this GitHub action;
  2. Create a new branch from the one that was used to create a release (e.g., create dev from main);
  3. Push any change to the new branch;
  4. Observe that your release is now automatically drafted.

Expected behavior
Previously created release must stay undrafted and unchanged.

Additional context
I read the documentation on your GitHub action and did not find any related option that could be causing my case.

commented

Found somewhat of a similar issue:
#317

However, my action does not even run for dev branch. But if I push anything to the branch, the release created from main gets drafted anyway.

commented

Not sure this is the action doing this as opposed to GitHub. If the action isn't even running when a commit is pushed to the new branch I don't think it's the action. I'd recommend checking your repo settings to make sure you don't have a rule setup.

commented

... If the action isn't even running when a commit is pushed to the new branch I don't think it's the action. I'd recommend checking your repo settings to make sure you don't have a rule setup.

Sounds sensible. However there are no specific rules in my repository whatsoever. It is public and has no rulesets on anything.

commented

Could you send me a link to the repo with the issue?

commented

Yeah so this seems like the same github behavior as #317. I don't think there's anything we can do in the action about it.

Just want to reiterate this note from that thread in case it can help:

Generally, GitHub releases work best when you have a tag already and create a release from that. You can probably simplify your workflow by having a step before the release action which creates and pushes the tag.