neo4j-documentation / neo4j-documentation/docs-refresh
Generate nginx 301 redirects for renamed files
Open
@ggrossetie is already working on this.
Since Sep 3, 2020.
:wrench: infrastructure
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 18
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
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:
rewrite ^/developer/cypher-basics-i/$ /developer/cypher/beginner/ permanent;
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.