argoproj / argoproj/argo-workflows

Git Output Artifacts

Open
#6,986 3 comments 4 reactions 0 assignees View on GitHub
area/artifacts
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 15h
Merged PRs (30d)
138

Description

# Summary

Currently Git Artifact only supports input, providing support for output would be great. I can see this providing credentials is already supported via secrets, theoretically the minimum extra field required would be a commit message

# Use Cases

Easy workflows that needs to update remote git repositories, such as argocd configuration repos.

---

**Message from the maintainers**:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Contributor guide

Open the contributing guide

Research direction

The issue names Git Artifact input support but no files, tests, or entry points. Start by locating the existing Git Artifact implementation and its input handling, then determine how output artifacts, credentials, repository updates, and commit messages should be specified. Done means a workflow can update a remote Git repository through the artifact and the behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go, kubernetes
Domain
backend, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.