Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Portacle Update Should Consider Only Tagged Releases #92

Open
Shinmera opened this issue Aug 29, 2018 · 0 comments
Open

Portacle Update Should Consider Only Tagged Releases #92

Shinmera opened this issue Aug 29, 2018 · 0 comments
Labels
elisp Problems related to the elisp code shipped with Portacle

Comments

@Shinmera
Copy link
Member

Shinmera commented Aug 29, 2018 •
edited

We should start tagging releases in the other repositories as well, and have portacle-update only update to the latest tag to avoid developmental changes ending up in user's installations.

At least it should only consider tags by default and allow git head by an extra argument. Would also be useful to let the user roll back to previous tags.
@Shinmera Shinmera added the elisp Problems related to the elisp code shipped with Portacle label Aug 29, 2018
@Shinmera Shinmera mentioned this issue Nov 15, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
elisp Problems related to the elisp code shipped with Portacle
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Shinmera