Skip to content
This repository was archived by the owner on Oct 6, 2025. It is now read-only.

Commit ff8c119

Browse files
authored
chore: update the Readme file for migration (#787)
Signed-off-by: Leonardo Luz Almeida <[email protected]>
1 parent 9068f90 commit ff8c119

File tree

1 file changed

+7
-50
lines changed

1 file changed

+7
-50
lines changed

README.md

Lines changed: 7 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,52 +1,9 @@
1-
# Ongoing migration
2-
The gitops-engine repository is migrating to https://github.com/argoproj/argo-cd.
1+
# Update September 24th 2025
32

4-
As part of this migration, we are going to:
3+
This repository is now closed for new commits. The codebase and its git
4+
history have been migrated to the [Argo CD
5+
repository](https://github.com/argoproj/argo-cd) under the
6+
gitops-engine directory.
57

6-
- close PRs with no updates older than 1 year
7-
- ask ppl to update the remaining PRs that had some update in the last year but are outdated.
8-
- review the pending recent open PRs that we deem important
9-
10-
Hold on your PRs until the migration is complete.
11-
12-
# GitOps Engine
13-
14-
Various GitOps operators address different use-cases and provide different user experiences but all have similar set of core features. The team behind
15-
[Argo CD](https://github.com/argoproj/argo-cd) has implemented a reusable library that implements core GitOps features:
16-
17-
- Kubernetes resource cache ✅
18-
- Resources reconciliation ✅
19-
- Sync Planning ✅
20-
- Access to Git repositories
21-
- Manifest Generation
22-
23-
## Proposals, specifications and ideas
24-
25-
Do you want to propose one more feature and want to enhance the existing one?
26-
Proposals and ideas are in markdown docs in the [`specs/`](specs/) directory.
27-
To create a new proposal, simply copy the spec [`template`](specs/template.md),
28-
name the file corresponding to the title of your proposal, and place it in the
29-
`specs/` directory.
30-
31-
A good starting point to understand the structure is the [GitOps Engine Design spec](specs/design.md).
32-
33-
We tried to answer frequently asked question in a [separate FAQ document](docs/faq.md).
34-
35-
## Governance
36-
37-
This project is licensed under the [Apache 2 license](LICENSE).
38-
39-
The GitOps Engine follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
40-
41-
## Get involved
42-
43-
If you are as excited about GitOps and one common engine for it as much as we are, please get in touch. If you want to write code that's great, if you want to share feedback, ideas and use-cases, that's great too.
44-
45-
Find us on the [#argo-cd-contributors][argo-cd-contributors-slack] on CNCF Slack (get an [invite here][cncf-slack]).
46-
47-
[argo-cd-contributors-slack]: https://cloud-native.slack.com/archives/C020XM04CUW
48-
[cncf-slack]: https://slack.cncf.io/
49-
50-
### Contributing to the effort
51-
52-
At this stage we are interested in feedback, use-cases and help on the GitOps Engine.
8+
If you have open PRs or Issues in this repo and believe it is
9+
important, please reopen it in Argo CD.

0 commit comments

Comments
 (0)