Browse Source

Update post & screenshots

pull/25640/head
enisn 4 months ago
parent
commit
ccc2f31440
No known key found for this signature in database GPG Key ID: A052619F04155D1C
  1. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-commit-message.gif
  2. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-commit-message.png
  3. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-review-details.png
  4. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-review.png
  5. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-branch-and-stash.png
  6. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-changes-and-diff.png
  7. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/github-issue-to-agent.png
  8. BIN
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/github-pr-requested-changes.png
  9. 8
      docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/post.md

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-commit-message.gif

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-commit-message.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 58 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-review-details.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-ai-review.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

After

Width:  |  Height:  |  Size: 63 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-branch-and-stash.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 58 KiB

After

Width:  |  Height:  |  Size: 35 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/git-changes-and-diff.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 56 KiB

After

Width:  |  Height:  |  Size: 174 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/github-issue-to-agent.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 57 KiB

BIN
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/github-pr-requested-changes.png

Binary file not shown.

Before

Width:  |  Height:  |  Size: 58 KiB

8
docs/en/Community-Articles/2026-06-18-deep-dive-6-abp-studio-git-integration/post.md

@ -72,7 +72,7 @@ I still want to choose which files belong together. I still want the commit mess
ABP Studio keeps that flow visible. I can select the files I want, write a summary and description, and commit to the current branch. When AI is enabled, Studio can generate a commit message from the selected diffs.
![Generating a commit message from selected changes](git-ai-commit-message.png)
![Generating a commit message from selected changes](git-ai-commit-message.gif)
I like this because it keeps the AI help close to the actual diff.
@ -120,6 +120,9 @@ ABP Studio supports that with AI review on selected Git changes.
![AI review suggestions on selected Git changes](git-ai-review.png)
![AI review suggestions on selected Git changes](git-ai-review-details.png)
The useful part is that the review is attached to the diff. Suggestions and notes appear near the changed lines, and if there is something I want the agent to handle, I can send those review notes to ABP Agent.
That changes the feel of the workflow.
@ -140,7 +143,7 @@ ABP Studio can bring GitHub issues into the Git area.
I can filter issues, open one, read the description and comments, create a branch for that issue, and send the issue context to ABP Agent.
![Creating a branch from a GitHub issue and sending it to ABP Agent](github-issue-to-agent.png)
That makes the workflow feel natural:
@ -160,7 +163,6 @@ Pull request feedback is another place where Git integration helps the AI workfl
When I open a pull request inside ABP Studio, I can see the PR title, branches, comments, reviews, and requested changes. If I am not on the PR branch, Studio can switch to it. Then I can choose which comments or requested changes should be included and send that context to ABP Agent.
![Requested changes from a GitHub pull request sent to ABP Agent](github-pr-requested-changes.png)
This is the workflow I want when a reviewer asks for changes:

Loading…
Cancel
Save