Consider renaming the caution git remote #238
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform#238
Loading…
Add table
Add a link
Reference in a new issue
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?
using
cautionon the command line may be needlessly overloaded, between an installed executablecautionand and thecautionremote.For example, to follow the quickstart docs, after installation:
https://docs.caution.co/quickstart/fully-managed/#initialize-the-application
caution init(running the executable)followed by https://docs.caution.co/quickstart/fully-managed/#deploy-the-application
git push caution main(wherecautionis now a remote)It is probably trivial to rename the remote to something like
caution_remoteor similar.By this logic
git push origin HEADshould be renamed togit push origin-remote HEAD. I don't think it makes sense to do this change.