Last 12 weeks · 1 commit
5 of 6 standards met
Description Passing paths to the end of the git log call, allows analyzing commits on a package-by-package basis in a monorepo. I have a PR open in as well, though here the git log command was being used, and they've had an open PR for this since 2023, since it's small, I just re-implimented it. was using which I got support added to, if it would be preferable to keep the command external. This serves as a good basis if further monorepo features would be welcome. Linked Issues Additional context
Reason for change I see the ci actions and README.md still uses the older version of actions/setup-node and actions/setup-node. https://github.com/actions/setup-node/releases https://github.com/actions/checkout/releases I wonder if it would be worth updating the ci and README to the latest versions. Impact Most of the major changes relates to the GitHub runner version. This would impact users running self hosted runners that are outdated. If this is not needed / desired, feel free to close this issue :)
Repository: antfu/changelogithub. Description: Generate changelog for GitHub Stars: 916, Forks: 54. Primary language: TypeScript. Languages: TypeScript (86%), JavaScript (14%). License: MIT. Topics: changelog, github, github-actions, release. Latest release: v14.0.0 (3mo ago). Open PRs: 2, open issues: 8. Last activity: 2d ago. Community health: 85%. Top contributors: antfu, innocenzi, frostming, hyoban, Waleed-KH, hrynevychroman, croatialu, LarchLiu, AlexVipond, Intevel and others.
TypeScript
Please be aware that vibe-coding contributions are 🚫 STRICTLY PROHIBITED. We are humans behind these open source projects, trying hard to maintain good quality and a healthy community. Not only do vibe-coding contributions pollute the code, but they also drain A LOT of unnecessary energy and time from maintainers and toxify the community and collaboration. All vibe-coded, AI-generated PRs will be rejected and closed without further notice. In severe cases, your account might be banned organization-wide and reported to GitHub. PLEASE SHOW SOME RESPECT and do not do so. Before submitting the PR, please make sure you do the following: Read the Contributing Guide. Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. Provide a description in this PR that addresses what the PR is solving and WHY**, or reference the issue that it solves (e.g. ). Ideally, include relevant tests that fail without this PR but pass with it. [X]