feat: add support for skipping the content of updated files. #267
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!267
Loading…
Reference in a new issue
No description provided.
Delete branch "aronsky/feat-skip-content-on-update"
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?
update_filecurrently returns the base64-encoded file contents in the response. In a lot of cases, this is redundant, yet the agent is forced to read it - which wastes tokens. This PR introduces a new option,skip_content, to the tool. When enabled, theUpdateFileFnfunction will strip the contents and the encoding from the response, prior to returning it.op1st Pipelines as Code is skipping this commit.
User aronsky is not allowed to trigger CI via pull_request in this repo.
/ok-to-test
op1st Pipelines as Code/forgejo-mcp-code-scans-4dp84 is running.
Starting Pipelinerun forgejo-mcp-code-scans-4dp84 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-4dp84 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-knr6z is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-knr6z in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-knr6z -fop1st Pipelines as Code/forgejo-mcp-code-scans-4dp84 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
@aronsky, thanks for making this contribution. I see what you want to do! +1
/triage
op1st Pipelines as Code/forgejo-mcp-on-pull-request-knr6z has failed.
Task Statuses:
fetch-source
commit-title-check
build-and-test
Failure snippet:
task commit-title-check has the status "Failed":op1st Pipelines as Code/forgejo-mcp-code-scans-5q56g is running.
Starting Pipelinerun forgejo-mcp-code-scans-5q56g in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-5q56g -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-cn5mc is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-cn5mc in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-cn5mc -fop1st Pipelines as Code/forgejo-mcp-code-scans-5q56g has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-cn5mc has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-g54l5 is running.
Starting Pipelinerun forgejo-mcp-code-scans-g54l5 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-g54l5 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-4stvj is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-4stvj in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-4stvj -fop1st Pipelines as Code/forgejo-mcp-code-scans-g54l5 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-4stvj has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.