kemitix/git-next

Doesn't properly detect when dev or next are ahead #23

New issue

Closed

opened 2024-04-10 18:01:24 +01:00 by kemitix · 0 comments

kemitix commented

2024-04-10 18:01:24 +01:00

Owner

Rewrite the forge::forgejo::get_commit_history to loop over multiple pages to find the required parent commit, (i.e. on next loop until find main, on dev loop until find next). If the required parent commit isn't found then treat this as an error.

Rewrite the `forge::forgejo::get_commit_history` to loop over multiple pages to find the required parent commit, (i.e. on `next` loop until find `main`, on `dev` loop until find `next`). If the required parent commit isn't found then treat this as an error.

kemitix added the

label 2024-04-10 18:01:24 +01:00

kemitix referenced this issue from a commit

2024-04-10 20:45:14 +01:00

fix(server): Doesn't properly detect when dev or next are ahead

kemitix closed this issue

2024-04-10 20:46:21 +01:00

kemitix referenced this issue from a commit

2024-04-10 20:51:45 +01:00

fix(server): Doesn't properly detect when dev or next are ahead

kemitix self-assigned this 2024-04-11 18:24:12 +01:00

kemitix added this to the v0.1.0 - Dog Food milestone 2024-04-11 18:35:22 +01:00

kemitix added this to the Road to v1 - Forgejo & Github project 2024-04-13 14:42:04 +01:00

Sign in to join this conversation.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: kemitix/git-next#23

No description provided.