[GH-ISSUE #3100] Cannot Update Branch #1513

New issue

Closed

opened 2026-03-02 13:44:51 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:44:51 +03:00

Owner

Originally created by @adell444 on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3100

Description

The option to Update branch on my CIPP fork is no longer available. It still works for CIPP-API but not for CIPP. After click on "Sync Fork", it wants me to either discard commits (docs say not to do this) or to open a PR (haven't seen this before).

Environment data

Non-Sponsored Instance
Front End version number: 6.4.1
Back end version number: 7.0.1
Tried Tenant Cache Clear: no
Tried Token Cache Clear: no

Originally created by @adell444 on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3100 ### Description The option to Update branch on my CIPP fork is no longer available. It still works for CIPP-API but not for CIPP. After click on "Sync Fork", it wants me to either discard commits (docs say not to do this) or to open a PR (haven't seen this before). ![Screenshot 2025-01-10 at 16 06 26](https://github.com/user-attachments/assets/d140c824-7ce0-43ee-83b2-21bfab2336a8) ### Environment data ```PowerShell Non-Sponsored Instance Front End version number: 6.4.1 Back end version number: 7.0.1 Tried Tenant Cache Clear: no Tried Token Cache Clear: no ```

kerem

2026-03-02 13:44:51 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:44:52 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 11, 2025):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (Jan 11, 2025): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug." Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 13:44:52 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jan 11, 2025):

This is a support issue, not a bug. Only sponsors get support. You can try #community-help in our discord community.

@KelvinTegelaar commented on GitHub (Jan 11, 2025): This is a support issue, not a bug. Only sponsors get support. You can try #community-help in our discord community.

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

starred/CIPP#1513

No description provided.

Rows
Columns