denoland / denoland/deploy_feedback

[Bug]: Can't export playground code to a GitHub repo

Open
#674 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### Problem description

I have this private playground(`narrow-gecko-49`) that'd like to export to a GitHub so that i can link another repo to the project. Cannot delete because i have already set env vars to the project and as we know, Deno Deploy doesn't make easy to import variables.
When i tap on the export button either inside the playground or project settings, it fails but the repo gets created. I tried it 3x and same thing happen.
image
First time it happened was yesterday inside the playground but i didn't pay much attention to since inside repo, the deploy bot has already queued the deployment so i went ahead to clone the repo locally and made some changes.
image
It's been 19hours since the repo was created and the deployment is still pending
image

This morning, I have noticed that it works with new playgrounds but not this particular one

### Steps to reproduce

1. Go to https://dash.deno.com/account/projects
2. Create a new playground code
3. Create a simple api route with `npm:hono`
4. Save and deploy the code
5. Export

### Expected behavior

The export should be successful and deployment should work

### Environment

_No response_

### Possible solution

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the export flow from the dashboard project page using a new playground, an npm:hono API route, and deployment, then compare it with the named playground narrow-gecko-49. Check whether the GitHub repository creation, export completion, and deploy-bot queue each finish successfully; done means export reports success and deployment is no longer pending.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.