Skip to content

Rename «CPAN Author's Secure Development Guide», to «Perl Developer's …»#185

Open
sjn wants to merge 1 commit intomainfrom
cpan-author-guide
Open

Rename «CPAN Author's Secure Development Guide», to «Perl Developer's …»#185
sjn wants to merge 1 commit intomainfrom
cpan-author-guide

Conversation

@sjn
Copy link
Contributor

@sjn sjn commented Sep 15, 2025

Renamed file and updated redirection metadata.

@sjn sjn requested a review from robrwo September 15, 2025 18:33
@sjn sjn self-assigned this Sep 15, 2025
Copy link
Contributor

@robrwo robrwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks alright. As long as the old path redirects, I think it's fine I disagree with that: you'll lose the git commit history for it. Just change the title but keep the filename.

We should probably rename the randomness guide too (the title, not the file).

@@ -145,7 +149,7 @@ To help in this shift, CPANSec has put together several [guides](./) intended to

## License and use of this document
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be something that outlines major changes, perhaps even links to the github history at https://github.com/CPAN-Security/security.metacpan.org/commits/main/docs/guides/cpan-secure-development-guide.md

Actually, I am not against renaming the file, because the history will be lost.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't git log --follow work well enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants