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
Currently when I rename a page, I add a :page-aliases: attribute, manually write the nginx rewrite rules and raise a PR on the neo4j.com.
It would be great if we could automatically raise a PR with the renamed/redirected files that have changed since the last build.
For example, moving /modules/ROOT/pages/cypher-basics-i.adoc to modules/cypher/pages/beginner.adoc would need the following added to src/nginx/includes/neo4j.com.redirects in the neo4j.com repo:
Currently when I rename a page, I add a
:page-aliases:
attribute, manually write the nginx rewrite rules and raise a PR on the neo4j.com.It would be great if we could automatically raise a PR with the renamed/redirected files that have changed since the last build.
For example, moving
/modules/ROOT/pages/cypher-basics-i.adoc
tomodules/cypher/pages/beginner.adoc
would need the following added tosrc/nginx/includes/neo4j.com.redirects
in the neo4j.com repo:The text was updated successfully, but these errors were encountered: