Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate code references in CONTRIBUTING.md, README.md, and other internal dev docs #1321

Open
verytactical opened this issue Jan 14, 2025 · 1 comment
Assignees
Labels
ci/cd Continuous Integration: GitHub Actions, commit/push hooks and scripts infrastructure internal-documentation Internal documentation of the Tact compiler and the repository. Not to be confused with docs/
Milestone

Comments

@verytactical
Copy link
Contributor

References to files in CONTRIBUTING.md are going stale when files are moving around.

Add linter in prepush hook that reports if references in markdown files went stale.

@anton-trunov anton-trunov changed the title Validate code references in CONTRIBUTING.md Validate code references in CONTRIBUTING.md, README.md, and other internal dev docs Jan 14, 2025
@anton-trunov anton-trunov added the internal-documentation Internal documentation of the Tact compiler and the repository. Not to be confused with docs/ label Jan 14, 2025
@anton-trunov anton-trunov added this to the Doc: 2025-01 milestone Jan 14, 2025
@anton-trunov anton-trunov added infrastructure ci/cd Continuous Integration: GitHub Actions, commit/push hooks and scripts labels Jan 14, 2025
@anton-trunov
Copy link
Member

Looks like a duplicate of #755

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/cd Continuous Integration: GitHub Actions, commit/push hooks and scripts infrastructure internal-documentation Internal documentation of the Tact compiler and the repository. Not to be confused with docs/
Projects
None yet
Development

No branches or pull requests

3 participants