mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2228] CIPP Front end wont update #1151
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1151
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Intellium-Admin on GitHub (Mar 18, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2228
Description
We are having issues updating out Frontend
Tried to sync the fork. Even gone as far as recreating the token now following the below steps:
static web app instance > Manage deployment token > reset
grab the new token
go to github
go to the CIPP FRONTEND repo for your org
go to settings up the top
go to secrets and variables > actions
Add new repo secret and paste that new token in
Fork shows as up to date but CIPP frontend shows out of date.
Any ideas?
Environment data
@github-actions[bot] commented on GitHub (Mar 18, 2024):
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!".
@Intellium-Admin commented on GitHub (Mar 18, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@Intellium-Admin commented on GitHub (Mar 18, 2024):
@KelvinTegelaar commented on GitHub (Mar 18, 2024):
Nog a bug but support issue, if you are a sponsor please contact the helpdesk. The information for the helpdesk was in your welcome email :)