github-starred/cobalt
2
0
Fork 0
mirror of https://github.com/imputnet/cobalt.git synced 2026-03-09 15:24:14 -05:00
Code Issues 202 Packages Projects Releases Wiki Activity

[YouTube / Self-Hosting] Cookie question #819

New Issue
Open
opened 2025-11-09 09:59:05 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-09 09:59:05 -06:00
Owner
Copy Link

Originally created by @iambtshft on GitHub (May 2, 2025).

Question

Has anyone succeeded in setting up own instance with custom cookie for YouTube?

What I tried

Self hosted instance behind residential proxy, see Instance configuration.

I exported cookies from private browser session using this fork https://github.com/sertraline/Get-cookies.txt-LOCALLY-Cobalt?tab=readme-ov-file

And got a cookies.json with something like

{
    "youtube":[
        "PREF=xxxxxxxxx;SOCS=xxxxxxxxx;VISITOR_INFO1_LIVE=xxxxxxxxx;__Secure-1PSIDTS=xxxxxxxxxxx;__Secure-3PSIDTS=xxxxxxx;<OTHER_COOKIES>"
    ]
}

When I try to download any video using this setup I receive

{
    "status": "error",
    "error": {
        "code": "error.api.youtube.api_error"
    }
}

Container output

cobalt API ^ω^
~~~~~~
version: 10.9.4
commit: 4b9644ebdfbfe7bc6f7ec2d476692e3619cb59bd
branch: main
remote: imputnet/cobalt
start time: Fri, 02 May 2025 20:15:46 GMT
~~~~~~
url: <OMIT>
port: 9000

[✓] api keys loaded successfully!
[✓] cookies loaded successfully!
[✓] poToken & visitor_data loaded successfully!

If I remove cookies (comment out COOKIE_PATH) - everything works just fine. Am I missing something?

Note: I used the same approach with yt-dlp and everything has worked. So I assume there's an issue in youtube.js or the cookie handling in cobalt, not sure.

Instance configuration

services:
  cobalt-api:
    image: ghcr.io/imputnet/cobalt
    init: true
    read_only: true
    restart: unless-stopped
    container_name: cobalt-api
    ports:
      - 9000:9000/tcp
    environment:
      API_URL: "<OMIT>"
      API_KEY_URL: "file:///keys.json"
      API_AUTH_REQUIRED: 1
      API_EXTERNAL_PROXY: "<OMIT>"
      YOUTUBE_SESSION_SERVER: "http://host.docker.internal:8080/token"
      COOKIE_PATH: "/cookies.json"
    labels:
      - com.centurylinklabs.watchtower.scope=cobalt
    volumes:
      - ./keys.json:/keys.json:ro
      - ./cookies.json:/cookies.json:ro
    extra_hosts:
        - "host.docker.internal:host-gateway"
    depends_on:
      yt-session-generator:
        condition: service_started

  watchtower:
    image: ghcr.io/containrrr/watchtower
    restart: unless-stopped
    command: --cleanup --scope cobalt --interval 900 --include-restarting
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  yt-session-generator:
    image: ghcr.io/imputnet/yt-session-generator:webserver
    init: true
    restart: unless-stopped
    container_name: yt-session-generator
    ports:
      - 8080:8080/tcp
Originally created by @iambtshft on GitHub (May 2, 2025). ## Question Has anyone succeeded in setting up own instance with custom cookie for YouTube? ### What I tried Self hosted instance behind residential proxy, see Instance configuration. I exported cookies from private browser session using this fork https://github.com/sertraline/Get-cookies.txt-LOCALLY-Cobalt?tab=readme-ov-file And got a `cookies.json` with something like ``` { "youtube":[ "PREF=xxxxxxxxx;SOCS=xxxxxxxxx;VISITOR_INFO1_LIVE=xxxxxxxxx;__Secure-1PSIDTS=xxxxxxxxxxx;__Secure-3PSIDTS=xxxxxxx;<OTHER_COOKIES>" ] } ``` When I try to download any video using this setup I receive ``` { "status": "error", "error": { "code": "error.api.youtube.api_error" } } ``` Container output ``` cobalt API ^ω^ ~~~~~~ version: 10.9.4 commit: 4b9644ebdfbfe7bc6f7ec2d476692e3619cb59bd branch: main remote: imputnet/cobalt start time: Fri, 02 May 2025 20:15:46 GMT ~~~~~~ url: <OMIT> port: 9000 [✓] api keys loaded successfully! [✓] cookies loaded successfully! [✓] poToken & visitor_data loaded successfully! ``` If I remove cookies (comment out `COOKIE_PATH`) - everything works just fine. Am I missing something? > Note: I used the same approach with [yt-dlp](https://github.com/yt-dlp/yt-dlp) and everything has worked. So I assume there's an issue in youtube.js or the cookie handling in cobalt, not sure. ### Instance configuration ```shell services: cobalt-api: image: ghcr.io/imputnet/cobalt init: true read_only: true restart: unless-stopped container_name: cobalt-api ports: - 9000:9000/tcp environment: API_URL: "<OMIT>" API_KEY_URL: "file:///keys.json" API_AUTH_REQUIRED: 1 API_EXTERNAL_PROXY: "<OMIT>" YOUTUBE_SESSION_SERVER: "http://host.docker.internal:8080/token" COOKIE_PATH: "/cookies.json" labels: - com.centurylinklabs.watchtower.scope=cobalt volumes: - ./keys.json:/keys.json:ro - ./cookies.json:/cookies.json:ro extra_hosts: - "host.docker.internal:host-gateway" depends_on: yt-session-generator: condition: service_started watchtower: image: ghcr.io/containrrr/watchtower restart: unless-stopped command: --cleanup --scope cobalt --interval 900 --include-restarting volumes: - /var/run/docker.sock:/var/run/docker.sock yt-session-generator: image: ghcr.io/imputnet/yt-session-generator:webserver init: true restart: unless-stopped container_name: yt-session-generator ports: - 8080:8080/tcp ```
GiteaMirror added the instance hosting help label 2025-11-09 09:59:05 -06:00
GiteaMirror commented 2025-11-09 09:59:06 -06:00
Author
Owner
Copy Link

@ansharyan03 commented on GitHub (May 4, 2025):

according to the latest commit logs YouTube cookies don't work anymore, I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution.

@ansharyan03 commented on GitHub (May 4, 2025): according to the latest commit logs YouTube cookies don't work anymore, I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution.
GiteaMirror commented 2025-11-09 09:59:06 -06:00
Author
Owner
Copy Link

@iambtshft commented on GitHub (May 12, 2025):

I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution.

I see that original session generator is deprecated as YouTube has changed the validation.
https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated

@iambtshft commented on GitHub (May 12, 2025): > I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution. I see that original session generator is deprecated as YouTube has changed the validation. https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated
GiteaMirror commented 2025-11-09 09:59:06 -06:00
Author
Owner
Copy Link

@ansharyan03 commented on GitHub (May 14, 2025):

I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution.

I see that original session generator is deprecated as YouTube has changed the validation. https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated

you just saved my life. invidious companion works with my proxy!

@ansharyan03 commented on GitHub (May 14, 2025): > > I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution. > > I see that original session generator is deprecated as YouTube has changed the validation. https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated you just saved my life. invidious companion works with my proxy!
GiteaMirror commented 2025-11-09 09:59:06 -06:00
Author
Owner
Copy Link

@TheK098 commented on GitHub (May 26, 2025):

@ansharyan03 do you mind sharing the instance configuration you used?

@TheK098 commented on GitHub (May 26, 2025): @ansharyan03 do you mind sharing the instance configuration you used?
GiteaMirror commented 2025-11-09 09:59:07 -06:00
Author
Owner
Copy Link

@ansharyan03 commented on GitHub (May 27, 2025):

@ansharyan03 do you mind sharing the instance configuration you used?

i'm actually no longer using the same configuration since we have to use invidious companion now, i'm backlogged with other stuff but currently trying to figure out how to load in bytes from the mp4 audio in a reasonable amount of time since the links you get from invidious companion seem to be optimal for loading chunks in parallel which i'm trying to figure out.

using invidious companion with a server api key and my https url for my proxy as the proxy environment variable, running deno dev server for now but will look into building the container with docker compose later when i actually figure out the link streaming

info here
https://github.com/iv-org/invidious-companion/wiki

@ansharyan03 commented on GitHub (May 27, 2025): > [@ansharyan03](https://github.com/ansharyan03) do you mind sharing the instance configuration you used? i'm actually no longer using the same configuration since we have to use invidious companion now, i'm backlogged with other stuff but currently trying to figure out how to load in bytes from the mp4 audio in a reasonable amount of time since the links you get from invidious companion seem to be optimal for loading chunks in parallel which i'm trying to figure out. using invidious companion with a server api key and my https url for my proxy as the proxy environment variable, running deno dev server for now but will look into building the container with docker compose later when i actually figure out the link streaming info here https://github.com/iv-org/invidious-companion/wiki
GiteaMirror commented 2025-11-09 09:59:07 -06:00
Author
Owner
Copy Link

@ansharyan03 commented on GitHub (May 27, 2025):

@ansharyan03 do you mind sharing the instance configuration you used?

before i had a session server and a proxy configured with env variables in my docker compose and the proxy would make it fail and i was tunneling my session server with http using ngrok to help my teammates access it temporarily

@ansharyan03 commented on GitHub (May 27, 2025): > [@ansharyan03](https://github.com/ansharyan03) do you mind sharing the instance configuration you used? before i had a session server and a proxy configured with env variables in my docker compose and the proxy would make it fail and i was tunneling my session server with http using ngrok to help my teammates access it temporarily
GiteaMirror commented 2025-11-09 09:59:07 -06:00
Author
Owner
Copy Link

@iambtshft commented on GitHub (May 27, 2025):

I had a quick look on companion but didn't find any easy way to get po_token, so there is no direct replacement session generator -> companion.

Another (potentially) working replacement for session generator is https://github.com/Brainicism/bgutil-ytdlp-pot-provider. It's mentioned on yt-dlp guide on PO token and provides docker container with API for PO Token generation. The only thing - it needs VISITOR_DATA / video id to correctly generate token. So might also not work without an additional changes on cobalt side.

@iambtshft commented on GitHub (May 27, 2025): I had a quick look on companion but didn't find any easy way to get po_token, so there is no direct replacement session generator -> companion. Another (potentially) working replacement for session generator is https://github.com/Brainicism/bgutil-ytdlp-pot-provider. It's mentioned on yt-dlp guide on PO token and provides docker container with API for PO Token generation. The only thing - it needs VISITOR_DATA / video id to correctly generate token. So might also not work without an additional changes on cobalt side.
GiteaMirror commented 2025-11-09 09:59:07 -06:00
Author
Owner
Copy Link

@mustfaunlu commented on GitHub (May 28, 2025):

same issue

@mustfaunlu commented on GitHub (May 28, 2025): same issue
GiteaMirror commented 2025-11-09 09:59:07 -06:00
Author
Owner
Copy Link

@TheK098 commented on GitHub (May 28, 2025):

Since the original session generator is deprecated, does anyone know what cobat tools is currently using to get these PO tokens? Or who we can ask to figure this out?

@TheK098 commented on GitHub (May 28, 2025): Since the original session generator is deprecated, does anyone know what cobat tools is currently using to get these PO tokens? Or who we can ask to figure this out?
GiteaMirror commented 2025-11-09 09:59:08 -06:00
Author
Owner
Copy Link

@wukko commented on GitHub (May 28, 2025):

cobalt is still using the same session generator, you can use our fork without any changes, if you wish: https://github.com/imputnet/yt-session-generator

@wukko commented on GitHub (May 28, 2025): cobalt is still using the same session generator, you can use our fork without any changes, if you wish: https://github.com/imputnet/yt-session-generator
GiteaMirror commented 2025-11-09 09:59:08 -06:00
Author
Owner
Copy Link

@Gareryer commented on GitHub (May 28, 2025):

The YT Session Generator seems not to be working perfectly, though.

services:
    cobalt-api:
        image: ghcr.io/imputnet/cobalt:11

        init: true
        read_only: true
        restart: unless-stopped
        container_name: cobalt

        ports:
            - 8088:9000/tcp
        environment:
            API_URL: "https://cobalt.website.com/"
            API_AUTH_REQUIRED: 1
            API_KEY_URL: "file:///keys.json"
            TURNSTILE_SITEKEY: "0xxxxxxxxxxxxxxxxxxxxxxP" # use your key
            TURNSTILE_SECRET: "0xxxxxxxxxxxxxxxxxxxxxx4" # use your key
            JWT_SECRET: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
            YOUTUBE_SESSION_SERVER: "http://host.docker.internal:8089/token"
            COOKIE_PATH: "/cookies.json"
        labels:
            - com.centurylinklabs.watchtower.scope=cobalt
        volumes:
            - ./cookies.json:/cookies.json
            - ./keys.json:/keys.json:ro
        extra_hosts:
            - "host.docker.internal:host-gateway"
        depends_on:
          yt-session-generator:
            condition: service_started

    watchtower:
        image: ghcr.io/containrrr/watchtower
        restart: unless-stopped
        command: --cleanup --scope cobalt --interval 900 --include-restarting
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock

    yt-session-generator:
        image: ghcr.io/imputnet/yt-session-generator:webserver
        init: true
        restart: unless-stopped
        container_name: yt-session-generator
        ports:
          - 8089:8080/tcp

With the above setup i keep getting this error

yt-session-generator  | 2025/05/29 21:48:30.487 [extractor] [INFO] update was succeessful
yt-session-generator  | 2025/05/29 21:53:30.543 [extractor] [INFO] update started
yt-session-generator  | 2025/05/29 21:53:34.606 [extractor] [INFO] new token: {"updated": 1748555614, "potoken": "MnSgFL75bMJwSqAsz5vDWEk6ePgSajdHGZguip0H1kHbhFoYsq9aoG0oDTdzQE_7A-Ib23nMKhX7x_3zfqzVeo6kN2Og76TI2cqx2qhqR15W4rHwpBmx4o9EsHYdnD7z_sEfazrQRSUjtcnHrBxrV2myHPrkYA==", "visitor_data": "CgtjeVcyTERsYmRTUSjcruPBBjIKCgJHQhIEGgAgMQ%3D%3D"}
yt-session-generator  | 2025/05/29 21:53:34.607 [extractor] [INFO] update was succeessful
cobalt                |
cobalt                | cobalt API ^ω^
cobalt                | ~~~~~~
cobalt                | version: 11.0.1
cobalt                | commit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
cobalt                | branch: main
cobalt                | remote: imputnet/cobalt
cobalt                | start time: Thu, 29 May 2025 21:33:08 GMT
cobalt                | ~~~~~~
cobalt                | url: https://website.com/
cobalt                | port: 9000
cobalt                |
cobalt                | [✓] internal tunnel handler running on 127.0.0.1:46297
cobalt                | [✓] api keys loaded successfully!
cobalt                | [✓] cookies loaded successfully!
cobalt                | [!] Failed loading poToken & visitor_data at 2025-05-29T21:33:18.557Z.
cobalt                | Error: TypeError: fetch failed
cobalt                |     at node:internal/deps/undici/undici:13510:13
cobalt                |     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
cobalt                |     at async loadSession (file:///app/src/processing/helpers/youtube-session.js:38:24) {
cobalt                |   [cause]: ConnectTimeoutError: Connect Timeout Error
cobalt                |       at onConnectTimeout (/app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:186:24)
cobalt                |       at /app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:133:46
cobalt                |       at Immediate._onImmediate (/app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:174:9)
cobalt                |       at process.processImmediate (node:internal/timers:505:21) {
cobalt                |     code: 'UND_ERR_CONNECT_TIMEOUT'
cobalt                |   }
cobalt                | }
cobalt                | [!] Failed loading poToken & visitor_data at 2025-05-29T21:38:18.596Z.
c
@Gareryer commented on GitHub (May 28, 2025): The YT Session Generator seems not to be working perfectly, though. ``` services: cobalt-api: image: ghcr.io/imputnet/cobalt:11 init: true read_only: true restart: unless-stopped container_name: cobalt ports: - 8088:9000/tcp environment: API_URL: "https://cobalt.website.com/" API_AUTH_REQUIRED: 1 API_KEY_URL: "file:///keys.json" TURNSTILE_SITEKEY: "0xxxxxxxxxxxxxxxxxxxxxxP" # use your key TURNSTILE_SECRET: "0xxxxxxxxxxxxxxxxxxxxxx4" # use your key JWT_SECRET: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" YOUTUBE_SESSION_SERVER: "http://host.docker.internal:8089/token" COOKIE_PATH: "/cookies.json" labels: - com.centurylinklabs.watchtower.scope=cobalt volumes: - ./cookies.json:/cookies.json - ./keys.json:/keys.json:ro extra_hosts: - "host.docker.internal:host-gateway" depends_on: yt-session-generator: condition: service_started watchtower: image: ghcr.io/containrrr/watchtower restart: unless-stopped command: --cleanup --scope cobalt --interval 900 --include-restarting volumes: - /var/run/docker.sock:/var/run/docker.sock yt-session-generator: image: ghcr.io/imputnet/yt-session-generator:webserver init: true restart: unless-stopped container_name: yt-session-generator ports: - 8089:8080/tcp ``` With the above setup i keep getting this error ``` yt-session-generator | 2025/05/29 21:48:30.487 [extractor] [INFO] update was succeessful yt-session-generator | 2025/05/29 21:53:30.543 [extractor] [INFO] update started yt-session-generator | 2025/05/29 21:53:34.606 [extractor] [INFO] new token: {"updated": 1748555614, "potoken": "MnSgFL75bMJwSqAsz5vDWEk6ePgSajdHGZguip0H1kHbhFoYsq9aoG0oDTdzQE_7A-Ib23nMKhX7x_3zfqzVeo6kN2Og76TI2cqx2qhqR15W4rHwpBmx4o9EsHYdnD7z_sEfazrQRSUjtcnHrBxrV2myHPrkYA==", "visitor_data": "CgtjeVcyTERsYmRTUSjcruPBBjIKCgJHQhIEGgAgMQ%3D%3D"} yt-session-generator | 2025/05/29 21:53:34.607 [extractor] [INFO] update was succeessful cobalt | cobalt | cobalt API ^ω^ cobalt | ~~~~~~ cobalt | version: 11.0.1 cobalt | commit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx cobalt | branch: main cobalt | remote: imputnet/cobalt cobalt | start time: Thu, 29 May 2025 21:33:08 GMT cobalt | ~~~~~~ cobalt | url: https://website.com/ cobalt | port: 9000 cobalt | cobalt | [✓] internal tunnel handler running on 127.0.0.1:46297 cobalt | [✓] api keys loaded successfully! cobalt | [✓] cookies loaded successfully! cobalt | [!] Failed loading poToken & visitor_data at 2025-05-29T21:33:18.557Z. cobalt | Error: TypeError: fetch failed cobalt | at node:internal/deps/undici/undici:13510:13 cobalt | at process.processTicksAndRejections (node:internal/process/task_queues:105:5) cobalt | at async loadSession (file:///app/src/processing/helpers/youtube-session.js:38:24) { cobalt | [cause]: ConnectTimeoutError: Connect Timeout Error cobalt | at onConnectTimeout (/app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:186:24) cobalt | at /app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:133:46 cobalt | at Immediate._onImmediate (/app/node_modules/.pnpm/undici@5.28.4/node_modules/undici/lib/core/connect.js:174:9) cobalt | at process.processImmediate (node:internal/timers:505:21) { cobalt | code: 'UND_ERR_CONNECT_TIMEOUT' cobalt | } cobalt | } cobalt | [!] Failed loading poToken & visitor_data at 2025-05-29T21:38:18.596Z. c ```
GiteaMirror commented 2025-11-09 09:59:08 -06:00
Author
Owner
Copy Link

@MCJack123 commented on GitHub (Jun 5, 2025):

Having the same issue on my instance, set up the session token generator & imported cookies, but still getting the API error described above. I'm using a DigitalOcean VPS without a residential proxy (yet), but it's showing the API error instead of login error, so I doubt that's the issue here.

@MCJack123 commented on GitHub (Jun 5, 2025): Having the same issue on my instance, set up the session token generator & imported cookies, but still getting the API error described above. I'm using a DigitalOcean VPS without a residential proxy (yet), but it's showing the API error instead of login error, so I doubt that's the issue here.
GiteaMirror commented 2025-11-09 09:59:08 -06:00
Author
Owner
Copy Link

@Gareryer commented on GitHub (Jun 7, 2025):

Having the same issue on my instance, set up the session token generator & imported cookies, but still getting the API error described above. I'm using a DigitalOcean VPS without a residential proxy (yet), but it's showing the API error instead of login error, so I doubt that's the issue here.

Try this YAML

@Gareryer commented on GitHub (Jun 7, 2025): > Having the same issue on my instance, set up the session token generator & imported cookies, but still getting the API error described above. I'm using a DigitalOcean VPS without a residential proxy (yet), but it's showing the API error instead of login error, so I doubt that's the issue here. Try this [YAML](https://github.com/imputnet/cobalt/issues/1308#issuecomment-2945605139)
GiteaMirror commented 2025-11-09 09:59:09 -06:00
Author
Owner
Copy Link

@martipartydev commented on GitHub (Sep 9, 2025):

I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution.

I see that original session generator is deprecated as YouTube has changed the validation. https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated

you just saved my life. invidious companion works with my proxy!

what proxy provider are you using, also how much trafic is going thru your proxy

@martipartydev commented on GitHub (Sep 9, 2025): > > > I'm also using a residential proxy and get api.fetch.fail errors when using a session server hosted on my own computer so I'm also actively looking for a solution. > > > > > > I see that original session generator is deprecated as YouTube has changed the validation. https://github.com/iv-org/youtube-trusted-session-generator?tab=readme-ov-file#tool-is-deprecated > > you just saved my life. invidious companion works with my proxy! what proxy provider are you using, also how much trafic is going thru your proxy
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
3rd party app support
bug
can reproduce
can't reproduce
documentation
duplicate
feature request
help wanted
instance hosting help
invalid
main instance issue
need more info
needs fixing
next major
not an issue
pull-request
Mirrored from GitHub Pull Request
 question
region lock issue
security
service request
skill issue
web ui
No Label instance hosting help
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/cobalt#819
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?