cory/tildefriends
5
6
Fork 2
Code Issues 35 Pull Requests Actions 1 Releases 31 Wiki Activity

A small suggestion from a lazy person #110

New Issue
Closed
opened 2025-02-20 13:53:22 -05:00 by Russbear · 3 comments
Russbear commented 2025-02-20 13:53:22 -05:00
Copy Link

I suggest creating a branch Dev. There will be all these so-called hourly commits and there will be releases with each micro-update, and in Main, full versions will be summarized and posted.It is also advisable to remove unnecessary branches.Note: why from lazy because I am too lazy to build the application via Docker

I suggest creating a branch Dev. There will be all these so-called hourly commits and there will be releases with each micro-update, and in Main, full versions will be summarized and posted.It is also advisable to remove unnecessary branches.Note: why from lazy because I am too lazy to build the application via Docker
cory commented 2025-02-21 09:57:58 -05:00
Owner
Copy Link

Hmm, I'm not too keen on changing my workflow.

I don't know enough about how git works. If there were a latest_release tag that I updated with each release, and you had a checkout of that, would your working tree update when I updated the tag and you pulled? Would that work for you?

Hmm, I'm not too keen on changing my workflow. I don't know enough about how git works. If there were a `latest_release` tag that I updated with each release, and you had a checkout of that, would your working tree update when I updated the tag and you pulled? Would that work for you?
Russbear commented 2025-02-22 06:55:07 -05:00
Author
Copy Link

If I understood you correctly, then I agree! As I understood, you want to release a version with each micro-update (commit)

If I understood you correctly, then I agree! As I understood, you want to release a version with each micro-update (commit)
cory commented 2025-02-22 11:33:12 -05:00
Owner
Copy Link

OK, I added a latest_release tag, which I'll keep up with the monthly v0.0.27-style releases. I like this compromise.

For me it's about things like active development happening up front and out in the open. You won't find that I've been off working in some branch you didn't realize existed, and definitely not in one on my laptop that I forgot to push. Plus I've gotten this far without having to diverge for very long on a feature branch, and I'd like to continue to avoid that. We can take this thing wherever we want with bite-size improvements ship of Theseus-style. If it gets too far from "working" it's hard to come back.</ramble>

OK, I added a `latest_release` tag, which I'll keep up with the monthly v0.0.27-style releases. I like this compromise. For me it's about things like active development happening up front and out in the open. You won't find that I've been off working in some branch you didn't realize existed, and definitely not in one on my laptop that I forgot to push. Plus I've gotten this far without having to diverge for very long on a feature branch, and I'd like to continue to avoid that. We can take this thing wherever we want with bite-size improvements ship of Theseus-style. If it gets too far from "working" it's hard to come back.&lt;/ramble&gt;
👍 1
cory closed this issue 2025-02-22 11:33:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
cory
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cory/tildefriends#110
No description provided.
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?