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

PR/merging question. #1166

Open
GregWhiteyBialas opened this issue Dec 19, 2023 · 1 comment · May be fixed by #1446
Open

PR/merging question. #1166

GregWhiteyBialas opened this issue Dec 19, 2023 · 1 comment · May be fixed by #1446
Assignees
Labels

Comments

@GregWhiteyBialas
Copy link

Hi!

In last year I have created PR which was merged and I was under impression (maybe wrong, no promises were made ;) ) that it will be merged "further" (to branch 4.4 and later to master).

Case is that in our deploys we are relaying on changes in this PR. So right now in our downstream fork we are stuck with version 4.4. To use newer versions I have to port this changes to newer downstream branch. However if this will be merged to master and used in all upcoming releases, I can happily delete downstream fork, and use latest version of Wazuh.

Is it possible to merge this into master? If yes, what's needs to be done? If no, what's needs to be done to make this happen?

@jonhattan
Copy link

That was a great change and it's a pity it didn't enter master -- I guess it was by mistake. Perhaps creating a new PR against master may help move this forward.

@YisDav YisDav self-assigned this Oct 25, 2024
@YisDav YisDav linked a pull request Oct 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

4 participants