Fix Git Flow
This commit is contained in:
+12
-7
@@ -1,12 +1,5 @@
|
||||
# Changelog
|
||||
|
||||
## Unreleased
|
||||
|
||||
- Fixed existing Gitea remote setup so `owner/name` connections can use the
|
||||
machine's configured SSH key instead of always forcing HTTPS authentication.
|
||||
- Added an explicit SSH/HTTPS clone protocol choice and optional
|
||||
`GITEA_SSH_USER`/`GITEA_SSH_PORT` configuration.
|
||||
|
||||
All notable changes to this project will be documented in this file.
|
||||
|
||||
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
|
||||
@@ -18,6 +11,18 @@ The format is based on Keep a Changelog, and this project adheres to Semantic Ve
|
||||
- Added startup onboarding for existing local repositories that have no remote configured.
|
||||
- Added provider selection to connect a local repository to an existing GitHub or Gitea remote repository.
|
||||
- Added optional post-connection push to set upstream tracking after configuring `origin`.
|
||||
- Added Gitea create-or-connect-and-sync actions for directories both with and
|
||||
without an existing local Git repository.
|
||||
- Added history-aware synchronization with fast-forward, merge,
|
||||
replace-local-with-backup, and force-push-with-lease behavior.
|
||||
- Added a conditional action for disconnecting local remote configuration.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Fixed existing Gitea remote setup so `owner/name` connections can use the
|
||||
machine's configured SSH key instead of always forcing HTTPS authentication.
|
||||
- Fixed synchronization of unborn repositories, which previously attempted to
|
||||
push a nonexistent `main` ref.
|
||||
|
||||
## [0.2.0] - 2026-02-15
|
||||
|
||||
|
||||
Reference in New Issue
Block a user