Skip to content

Conversation

@DevIos01
Copy link
Member

@DevIos01 DevIos01 commented Mar 6, 2025

This PR introduces an improved workflow for updating game code directly from the Sprig Editor after publishing. Instead of manually creating new pull requests, users can now commit their changes directly to their existing PR.

image

a new way to update your game directly from sprig editor after publishing the game.
@DevIos01 DevIos01 requested a review from JosiasAurel March 6, 2025 18:31
@DevIos01 DevIos01 self-assigned this Mar 6, 2025
@vercel
Copy link

vercel bot commented Mar 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sprig ❌ Failed (Inspect) Mar 6, 2025 6:32pm

Copy link
Contributor

@grymmy grymmy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine but would love for this to be tested by someone independently to ensure we cover all angles... @LucasHT22 any chance you could help w/ this?

@grymmy
Copy link
Contributor

grymmy commented Apr 28, 2025

@DevIos01 is this like, landable?

@DevIos01
Copy link
Member Author

@DevIos01 is this like, landable?

The frontend and core functionality have been completed. but there is a known issue that remains unfixed, where if a user has an existing Sprig repository fork, the publish action fails. Landing is not possible without fixing or reworking the related logic.

@whatwareweb whatwareweb added feature request New Feature or Request enhancement New feature or request and removed feature request New Feature or Request labels Jul 25, 2025
@DevIos01 DevIos01 closed this Oct 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants