github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-05 19:18:16 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #509] [Netlify preview] Attach the preview url as a "status" to the commit #6202

New Issue
Open
opened 2026-04-20 16:48:05 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 16:48:05 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/509

Original issue by dpschen on 2022-05-21T14:21:52.000Z

I don't know how long netlify's preview urls are kept up, but I think they only live a certain time.

Another idea might be to attache the preview url as a "status" to the commit: https://kolaente.dev/api/swagger#/repository/repoCreateStatus
That way it would show up in the PR like the drone runs.

Originally posted by @konrad in https://kolaente.dev/vikunja/frontend/issues/1585#issuecomment-26712

Original issue on Gitea

@kolaente commented on 2022-05-22T14:36:03.000Z:

Since cloudflare pages now allows deployments via their cli we could think about migrating to that instead. AFAIK their preview environment are never really deleted and are accessible on a per-commit basis.

dpschen commented on 2022-05-22T14:38:43.000Z:

That's cool :)

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/509 _Original issue by dpschen on 2022-05-21T14:21:52.000Z_ I don't know how long netlify's preview urls are kept up, but I think they only live a certain time. Another idea might be to attache the preview url as a "status" to the commit: https://kolaente.dev/api/swagger#/repository/repoCreateStatus That way it would show up in the PR like the drone runs. _Originally posted by @konrad in https://kolaente.dev/vikunja/frontend/issues/1585#issuecomment-26712_ [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1923) --- _**@kolaente** commented on 2022-05-22T14:36:03.000Z_: Since [cloudflare pages](https://pages.dev) now allows deployments via their cli we could think about migrating to that instead. AFAIK their [preview environment](https://developers.cloudflare.com/pages/platform/preview-deployments/) are never really deleted and are accessible on a per-commit basis. --- _**dpschen** commented on 2022-05-22T14:38:43.000Z_: That's cool :)
GiteaMirror added the area/internal-code label 2026-04-20 16:48:05 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/internal-code
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6202
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?