Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix missing release branch when looking for commits#1055

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

sdb9696
Copy link
Contributor

The default responses per page of 30 can cause the release branch to be missed out of the query results during the check for commits in the release branch.

This causes WARNING:merge commit was not found in the release branch or tagged git history and no rebased SHA comment was found.#971

This PR sets the default query response size to 100 to reduce the likelihood of this happening. A more permanent solution could be to restrict the branches query to the required branch.

@olleolleolle
Copy link
Collaborator

Right, 30 branches lying around is nothing. Even 100 could be very little. But offering the default options to the API request should be uncontroversial.

@sdb9696
Copy link
ContributorAuthor

The query also brings back deleted branches which doesn’t help. I’ll look shortly to see if there’s a parameter to control that.

@sdb9696
Copy link
ContributorAuthor

The latest commit iterates the pages so no 100 limit either.

@sdb9696
Copy link
ContributorAuthor

Hey@olleolleolle, any chance of getting this merged? I’m also happy to address any suggestions if you have any.

Copy link
Collaborator

@olleolleolleolleolleolle left a comment
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I looked in detail at the individual code changes.

I think the fix is good, even with the early return, this method should not need other than the named branch, really. Any such changes are outside the scope of this repair.

Co-authored-by: Olle Jonsson <olle.jonsson@gmail.com>
@sdb9696
Copy link
ContributorAuthor

Thanks, I've applied the suggestions and retested the code and all works ok.

@sdb9696
Copy link
ContributorAuthor

Hey@olleolleolle, are you ok to merge this now?

@sdb9696
Copy link
ContributorAuthor

Hey@olleolleolle, sorry to pester but could we get this merged?

@olleolleolleolleolleolle merged commit15516a6 intogithub-changelog-generator:masterNov 26, 2024
3 checks passed
@sdb9696sdb9696 deleted the fix/missing_branches branchNovember 29, 2024 08:06
@sdb9696
Copy link
ContributorAuthor

Thanks for merging@olleolleolle. Do you plan to do a release anytime soon?

lazardjokovic reacted with thumbs up emoji

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@olleolleolleolleolleolleolleolleolle approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@sdb9696@olleolleolle

[8]ページ先頭

©2009-2025 Movatter.jp