brew/Library/Homebrew/test/dev-cmd/contributions_spec.rb

# frozen_string_literal: true

require "cmd/shared_examples/args_parse"
require "dev-cmd/contributions"

RSpec.describe Homebrew::DevCmd::Contributions do
  it_behaves_like "parseable arguments"
end
dev-cmd/contributions: Retrieve a user's repo contributions over time - Before each AGM it's currently a manual process for a PLC member to search commit logs and GitHub to figure out who contributed to Homebrew, so who should remain a member. - I noticed that [looking at commits for a user](https://github.com/Homebrew/homebrew-core/commits?author=issyl0&since=2022-01-01&until=2023-01-01) would not count `Co-Authored-By`, which happens a lot now there's an autosquash action on PRs in `Homebrew/homebrew-core`, say if someone fixed a formula's build or tests or whatever and then the PR got auto-merged. - Here's `brew contributions` that uses `git log` to be able to go back through all time or a specific time period (`--from`, `--to`). It's up to individual PLC discretion for "activity", but it does at least go some way to automating the data retrieval. - Example (I can use my username as `--email` because my username is in all of the email addresses that I use for committing to Homebrew): ``` $ brew contributions --email=issyl0 --repos=brew,core Person issyl0 directly authored 732 commits and co-authored 31 commits to brew, core in all time. ``` 2022-07-24 22:06:00 +01:00			`# frozen_string_literal: true`

			`require "cmd/shared_examples/args_parse"`
Port Homebrew::DevCmd::Contributions 2024-03-19 11:57:54 -07:00			`require "dev-cmd/contributions"`
dev-cmd/contributions: Retrieve a user's repo contributions over time - Before each AGM it's currently a manual process for a PLC member to search commit logs and GitHub to figure out who contributed to Homebrew, so who should remain a member. - I noticed that [looking at commits for a user](https://github.com/Homebrew/homebrew-core/commits?author=issyl0&since=2022-01-01&until=2023-01-01) would not count `Co-Authored-By`, which happens a lot now there's an autosquash action on PRs in `Homebrew/homebrew-core`, say if someone fixed a formula's build or tests or whatever and then the PR got auto-merged. - Here's `brew contributions` that uses `git log` to be able to go back through all time or a specific time period (`--from`, `--to`). It's up to individual PLC discretion for "activity", but it does at least go some way to automating the data retrieval. - Example (I can use my username as `--email` because my username is in all of the email addresses that I use for committing to Homebrew): ``` $ brew contributions --email=issyl0 --repos=brew,core Person issyl0 directly authored 732 commits and co-authored 31 commits to brew, core in all time. ``` 2022-07-24 22:06:00 +01:00
Port Homebrew::DevCmd::Contributions 2024-03-19 11:57:54 -07:00			`RSpec.describe Homebrew::DevCmd::Contributions do`
dev-cmd/contributions: Retrieve a user's repo contributions over time - Before each AGM it's currently a manual process for a PLC member to search commit logs and GitHub to figure out who contributed to Homebrew, so who should remain a member. - I noticed that [looking at commits for a user](https://github.com/Homebrew/homebrew-core/commits?author=issyl0&since=2022-01-01&until=2023-01-01) would not count `Co-Authored-By`, which happens a lot now there's an autosquash action on PRs in `Homebrew/homebrew-core`, say if someone fixed a formula's build or tests or whatever and then the PR got auto-merged. - Here's `brew contributions` that uses `git log` to be able to go back through all time or a specific time period (`--from`, `--to`). It's up to individual PLC discretion for "activity", but it does at least go some way to automating the data retrieval. - Example (I can use my username as `--email` because my username is in all of the email addresses that I use for committing to Homebrew): ``` $ brew contributions --email=issyl0 --repos=brew,core Person issyl0 directly authored 732 commits and co-authored 31 commits to brew, core in all time. ``` 2022-07-24 22:06:00 +01:00			`it_behaves_like "parseable arguments"`
			`end`