You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: