Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the process to bring upstream changes #2

Closed
Tracked by #1
AlexRuiz7 opened this issue Nov 16, 2022 · 1 comment · Fixed by #3
Closed
Tracked by #1

Define the process to bring upstream changes #2

AlexRuiz7 opened this issue Nov 16, 2022 · 1 comment · Fixed by #3
Assignees

Comments

@AlexRuiz7
Copy link
Member

AlexRuiz7 commented Nov 16, 2022

Description

To keep this repository up-to-date with the original OpenSearch Repository, we need to periodically sync the fork bringing here (fork) the new changes made in the original repository (upstream).

For that, we'll follow the strategy defined in this article. To minimize the conflicts between the repos, we'll use the rebase strategy, replaying our work on top of OpenSearch Dashboards features.

We want to sync the fork once a week at least, so we'll also need to automatize this process. For that, we'll use GitHub Actions, and this action in particular.

@AlexRuiz7 AlexRuiz7 linked a pull request Nov 16, 2022 that will close this issue
8 tasks
@AlexRuiz7 AlexRuiz7 self-assigned this Nov 16, 2022
@AlexRuiz7
Copy link
Member Author

We'll add this action, however, we'll see if it's possible to bring this, and other actions, to the Wazuh organization, so we can have control over the source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant