WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
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
Copy file name to clipboardExpand all lines: MAINTAINERS.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,11 @@ with the latest revision weekly. Nighthawk reuses large parts of Envoy's build
37
37
system and codebase, so keeping Nighthawk up to date with Envoy's changes is an
38
38
important maintenance task.
39
39
40
-
We use a utility script that will attempt to find the latest Envoy commit that
40
+
The update process can be completed by manually executing the steps documented on this [page](https://github.com/envoyproxy/nighthawk/blob/69321419308f36078037a05a6b12b9819368d413/docs/root/updating_envoy_dependency.md)**or** running a utility script. The rest of this page provides instructions for using the utility script.
41
+
42
+
### Run the utility script
43
+
44
+
The utility script will attempt to find the latest Envoy commit that
41
45
integrates cleanly with Nighthawk and create a Github branch with that
42
46
integration ready to merge. If it encounters a non-trivial Envoy commit
43
47
integration, it will prompt the user to resolve any errors before proceeding.
0 commit comments