Skip to content

πŸ›πŸ§‘β€πŸ’» - Release Deploy IssuesΒ #287

@efraespada

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Issue

Which platforms are affected?

Linux

Description

We need to improve the deployment system, as the changelog generated before starting the deployment is currently not being read correctly. When it is processed, the content is parsed incorrectly.

The changelog should be read starting from the Changelog title up to the top of the Additional Context section. All of this content must be used as the body of the new release that is created during the deployment process.

Additionally, when the deploy label is added to an issue to trigger the deployment, the issue should be automatically moved to the In Progress column. Initially, the issue is in the To Do column, but adding the deploy label must move it to In Progress. Once the issue deploy label is applied, the deployment process starts. This part is currently working as expected.

The problem occurs at the end of the process: when the deployment finishes successfully, a deployed label is added to the issue to indicate completion. At this point, the issue should be automatically closed, but this is not currently happening.

Reproducing the issue

Create a new release and deploy. It won't be automatically closed when the deployed label is applied.

git-board-flow Version

master

Relevant Log Output

Additional context and comments

No response

Metadata

Metadata

Assignees

Labels

100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions