Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BITBUCKET] Get Pull Request URL From Commit Message? #493

Closed
vovkanaz opened this issue Feb 12, 2024 · 1 comment
Closed

[BITBUCKET] Get Pull Request URL From Commit Message? #493

vovkanaz opened this issue Feb 12, 2024 · 1 comment
Assignees
Labels
feature/request New feature or request

Comments

@vovkanaz
Copy link

vovkanaz commented Feb 12, 2024

Is your feature request related to a problem? Please describe.
We Have this Commit message inside Bitbucket:

MERGED
Merged in BRANCH NAME pull request #50 commit_message

Describe the solution you'd like
Does Cliff support any ability for ingesting git PR/MR url inside CHANGELOG MD?

Describe alternatives you've considered

We've found LINK as this example, but still do not have clear info on how to align this with our case. It seems like we should parse our PR commit message to be able to ingest it inside CHANGELOG.md. But still haven't had success using such an approach.

Additional context

  1. How to ingest the result of this preprocessed message into the template? Or we should use post_processor? But a question is the same how to use it inside the template after processing?
  2. Also another question may be some thoughts about the automation process related to the automatic TAG creation using Bitbucket pipelines.
@vovkanaz vovkanaz added the feature/request New feature or request label Feb 12, 2024
Copy link

welcome bot commented Feb 12, 2024

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

Repository owner locked and limited conversation to collaborators Mar 2, 2024
@orhun orhun converted this issue into discussion #527 Mar 2, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
feature/request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants