You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SemanticDeveloper/SemanticDeveloper/README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,8 @@ The app integrates basic Git operations directly in the header. All actions use
105
105
- Stages all changes (`*`) and creates a commit with the provided message.
106
106
- Uses your Git config for name/email if available; otherwise falls back to a local signature like `<user>@local`.
107
107
- If there are no changes, you’ll get a friendly “No changes to commit.” notice.
108
+
- Automatically pushes the current branch to its tracked remote (defaults to `origin`).
109
+
- Optional: tick **Create Pull Request** to open your browser to a GitHub compare page after a successful push.
108
110
- New Branch…
109
111
- Creates and checks out a new branch based on the default branch when available.
110
112
- Behavior details:
@@ -113,20 +115,31 @@ The app integrates basic Git operations directly in the header. All actions use
113
115
- Example log: `Created and checked out 'feature-x' (based on origin/main).`
114
116
- Switch Branch…
115
117
- Checks out an existing branch by name (no automatic fetch/merge).
118
+
- Get Latest
119
+
- Fetches from the tracked remote (defaults to `origin`) and fast-forwards the current branch when possible.
120
+
- Requires the branch to track a remote counterpart; otherwise a helpful log message is shown.
121
+
- Stops early if a merge or rebase would be required (fast-forward only).
116
122
- Rollback Changes…
117
123
- Hard‑resets the working directory to `HEAD` and deletes untracked files.
118
124
- Prompts for confirmation since this discards local changes.
119
125
- Refresh
120
126
- Refreshes the branch label and the file tree’s Git status coloring.
121
127
128
+
Example workflow
129
+
1. Switch to an existing base branch (e.g., `main` or `master`).
130
+
2. Choose **Git ▾ → Get Latest** to fast-forward your local branch.
131
+
3. Use **Git ▾ → New Branch…** with your preferred naming convention (e.g., `feature/login-form`).
132
+
4. After making changes, select **Commit…**, enter a message, let the app push the branch for you, and optionally enable **Create Pull Request** to jump straight to GitHub once the push completes.
133
+
122
134
- Initialize Git…
123
135
- When the workspace is not a Git repo, an “Initialize Git…” button appears in the header.
124
136
- Initializes a repository in the selected folder, stages files, and attempts an initial commit (best‑effort).
125
137
- This is the same capability offered right after selecting a non‑repo folder.
126
138
127
139
Notes
128
-
- Operations are local and safe: no network is used except the optional `fetch` for “New Branch…”.
129
-
- Pull/push are not exposed in the UI. If desired, they can be added later.
140
+
- Operations are local unless a remote call is required (the optional `fetch` during “New Branch…”, the fast-forward fetch performed by “Get Latest”, and the push that runs after each commit).
141
+
- Open your workspace at the root of the Git repository (the folder containing `.git/`) so the app can detect and enable Git features; selecting a subdirectory skips the Git UI.
142
+
- Pull support is limited to fast-forwarding via **Get Latest**; pushing is still not exposed in the UI.
130
143
- On some Linux distros, libgit2 may require additional native dependencies. If the Git library can’t load, the UI will hide Git actions and log a helpful message.
0 commit comments