Prebuilds in Daytona

[Kiran1689]

/claim #82
fix #82

Writer's Checklist

Writing Structure

• Use short sentences and paragraphs, and include bucket brigades.
• Include more than two descriptive H2 headings to organize content.
• Capitalize headings according to the AP Stylebook
  (use this tool)
• Include an introduction with at least two paragraphs before the first H2
  section.
• Use appropriate formatting (bold, italic, underline), notes, quotes,
  TLDRs, and key points.
• Incorporate code elements and Markdown format where appropriate.
• Ensure at least one visual element per “screen” of the article
  (screenshots, diagrams, tables, graphs, lists, sidenotes, blockquotes).

Fact-Checking

• Verify all facts and data points included in the article.

Asset Management

• Save images in the /assets folder.
• Follow naming conventions:
  YYYYMMDD_title_of_the_article_IMG_NAME_NO.png.
• (Optional) Create a GitHub repo for the code referenced in the article and
  share it.
• (Optional) Include a link to this Loom video in the PR comments.

Interlinking

• Use CTRL+F to search for relevant keywords in:
  • Daytona Dotfiles Sitemap
  • Daytona Definitions Sitemap
• Interlink keywords using the appropriate URLs.

Glossary/Definitions

• Create new definition in /defitnitions folder.

Review and Edit

• Ensure articles address the needs of the target audience and their search
  intent.
• Read the article out loud to catch any awkward phrasing.
• Run the draft through Grammarly or a similar
  grammar tool.
• Double-check adherence to the style guide and repository guidelines.
• Use the name of the article for the title of the PR.

[Kiran1689]

@nkkko @mojafa

Include a section on breaking changes and necessary SQL commands for database migration.

Is this required for this article? As we are currently using Daytona v0.49

[Kiran1689]

@mojafa Can you please look into this.

[mojafa]

@nkkko @mojafa

Include a section on breaking changes and necessary SQL commands for database migration.

Is this required for this article? As we are currently using Daytona v0.49

@Kiran1689 I don't think so. Will work without it

[Kiran1689]

@mojafa @nkkko Any updates on this PR?

[mojafa]

@Kiran1689 just @ me goign forward. I did share a feedback

[mojafa]

Add the command to list gp (git providerS) or add gp as well.
like this :

[Kiran1689]

Updated @mojafa

[mojafa]

@Kiran1689 for a quick add, please add this in your references as well: https://www.daytona.io/dotfiles/boost-your-workspace-creation-with-prebuilds

[mojafa]

@nkkko as per the issue ticket you opened, we've since had v0.50, anything post the time the issue ticket was opened has changed. for instance, we no longer need to specify a git branch or a specific git provider when adding a prebuild. we also don't need this now:

Include a section on breaking changes and necessary SQL commands for database migration.

[Kiran1689]

@Kiran1689 for a quick add, please add this in your references as well: https://www.daytona.io/dotfiles/boost-your-workspace-creation-with-prebuilds

Added @mojafa