{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":723844404,"defaultBranch":"main","name":"go-vermock","ownerLogin":"Versent","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-11-26T22:26:11.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/11023632?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1711102201.0","currentOid":""},"activityList":{"items":[{"before":"02210b20f110b005d8691f367c0406fb27838a61","after":"ac9ea6898982a832a354ceb172a7e8df661e0245","ref":"refs/heads/mod-test","pushedAt":"2024-03-22T10:10:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"test: introduce basic tests for i/cmd/vermockgen\n\nPrior to this change, there were no test files for the package:\ngithub.com/Versent/go-vermock/internal/cmd/vermockgen.\n\nThis change introduces limited tests for SetFlags and Execute methods.","shortMessageHtmlLink":"test: introduce basic tests for i/cmd/vermockgen"}},{"before":null,"after":"02210b20f110b005d8691f367c0406fb27838a61","ref":"refs/heads/fgrosse-go-coverage-report","pushedAt":"2024-03-22T10:10:01.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: introduce fgrosse/go-coverage-report\n\nPrior to this change, the existing code coverage report step in the\nGitHub actions placed the report on the wiki, while this is good for a\nhistorical view it doesn't provide any immediate feedback during the\npull request review process.\n\nThis change introduces fgrosse/go-coverage-report, which is capable of\nparticipating in the conversation of the pull request.","shortMessageHtmlLink":"chore: introduce fgrosse/go-coverage-report"}},{"before":"ac9ea6898982a832a354ceb172a7e8df661e0245","after":"02210b20f110b005d8691f367c0406fb27838a61","ref":"refs/heads/mod-test","pushedAt":"2024-03-22T09:57:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: introduce fgrosse/go-coverage-report\n\nPrior to this change, the existing code coverage report step in the\nGitHub actions placed the report on the wiki, while this is good for a\nhistorical view it doesn't provide any immediate feedback during the\npull request review process.\n\nThis change introduces fgrosse/go-coverage-report, which is capable of\nparticipating in the conversation of the pull request.","shortMessageHtmlLink":"chore: introduce fgrosse/go-coverage-report"}},{"before":"81a63ae99229613e613168c2cf652363f4c1c546","after":"ac9ea6898982a832a354ceb172a7e8df661e0245","ref":"refs/heads/mod-test","pushedAt":"2024-03-22T09:46:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"test: introduce basic tests for i/cmd/vermockgen\n\nPrior to this change, there were no test files for the package:\ngithub.com/Versent/go-vermock/internal/cmd/vermockgen.\n\nThis change introduces limited tests for SetFlags and Execute methods.","shortMessageHtmlLink":"test: introduce basic tests for i/cmd/vermockgen"}},{"before":null,"after":"81a63ae99229613e613168c2cf652363f4c1c546","ref":"refs/heads/mod-test","pushedAt":"2024-03-22T09:39:27.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: update to go 1.21\n\nPrior to this change, we using go 1.20.\n\nThis change updates to go 1.21 and introduces the toolchain directive.\nWith this update the tools.go file is no longer required for the test\ncases and it also highlighted some missing go mod tidy commands in the\ntest cases.","shortMessageHtmlLink":"chore: update to go 1.21"}},{"before":"86a7c40b408a8d8fc49df9f5d50cc5e804a33b4f","after":null,"ref":"refs/heads/rename","pushedAt":"2024-01-10T22:55:42.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"283d082db990ce84a9adcd51d908f99a71534808","after":"b8d801a4d330f2d0b1e4e806fdffb152e0cacb91","ref":"refs/heads/main","pushedAt":"2024-01-10T22:55:41.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: rename package to vermock/vermockgen\n\nPrior to this change, this package had been given the same name as an\nother package which is already in widespread use within the community.\nThis does not cause a problem per se, but it does lead to aliasing\nshould a project choose use both or adopt one and migrate away from the\nother.  This aliasing can lead to ambiguity when a naming convention\nisn't agreed upon.  The problem can be even more difficult to diagnose\nwhen you consider multiple installed binaries with the same name.\n\nThis change could recommend a naming convention to address such\nsituations but we have decided to take the more drastic action of\nrenaming the whole package while we are still pre-v1.  This mean\nrenaming the module, GitHub repository, the packages (root package,\n./cmd/mockgen, ./internal/cmd/mockgen) and of course the README.","shortMessageHtmlLink":"chore: rename package to vermock/vermockgen"}},{"before":null,"after":"86a7c40b408a8d8fc49df9f5d50cc5e804a33b4f","ref":"refs/heads/rename","pushedAt":"2024-01-10T22:50:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: rename package to vermock/vermockgen\n\nPrior to this change, this package had been given the same name as an\nother package which is already in widespread use within the community.\nThis does not cause a problem per se, but it does lead to aliasing\nshould a project choose use both or adopt one and migrate away from the\nother.  This aliasing can lead to ambiguity when a naming convention\nisn't agreed upon.  The problem can be even more difficult to diagnose\nwhen you consider multiple installed binaries with the same name.\n\nThis change could recommend a naming convention to address such\nsituations but we have decided to take the more drastic action of\nrenaming the whole package while we are still pre-v1.  This mean\nrenaming the module, GitHub repository, the packages (root package,\n./cmd/mockgen, ./internal/cmd/mockgen) and of course the README.","shortMessageHtmlLink":"chore: rename package to vermock/vermockgen"}},{"before":"dfc30600c737b02420c42c150f1d856bbf0a0fb5","after":null,"ref":"refs/heads/fix-whitespace","pushedAt":"2023-12-22T06:23:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"da222c75fa61208061495fa315b9c0dc67722d75","after":"283d082db990ce84a9adcd51d908f99a71534808","ref":"refs/heads/main","pushedAt":"2023-12-22T06:23:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: correct indent in README code block\n\nPrior to this change, the indentation of a nested code block had been\ncorrupted.\n\nThis change ensures there are spaces to indent the ordered list and tabs\nto indent the code within the code block.","shortMessageHtmlLink":"chore: correct indent in README code block"}},{"before":"f3e0fb8370ffe4c8f263f9a73ba7af410bd5c419","after":"dfc30600c737b02420c42c150f1d856bbf0a0fb5","ref":"refs/heads/fix-whitespace","pushedAt":"2023-12-22T06:22:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"chore: correct indent in README code block\n\nPrior to this change, the indentation of a nested code block had been\ncorrupted.\n\nThis change ensures there are spaces to indent the ordered list and tabs\nto indent the code within the code block.","shortMessageHtmlLink":"chore: correct indent in README code block"}},{"before":null,"after":"f3e0fb8370ffe4c8f263f9a73ba7af410bd5c419","ref":"refs/heads/fix-whitespace","pushedAt":"2023-12-22T06:16:10.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): record code coverage for test scripts\n\nPrior to this change, the test scripts (under ./cmd/mockgen) would run\nthe command using go-run, which builds the mockgen binary and then runs\nit.  This meant that no code coverage was collected for these tests.\n\nThis change introduces a custom TestMain function that builds the binary\nwith the -cover option (new in go 1.20) which produces coverage data in\na binary format.  The go-test command can also produce data in the same\nformat when given the -test.gocoverdir option.  When the ./cmd/mockgen\ntests find this option, coverage for the script tests is enabled.  This\nallows us to then combine the coverage from the tests across all\npackages.  At this time, the go-test command doesn't appear to be able\nto do this automatically and the coverage reported is inaccurate.  To\ngenerate the combined coverage use the covdata tool after running\ngo-test:\n\n    mkdir \"$PWD/covdata\"\n    go test -cover ./... -test.gocoverdir=\"$PWD/covdata\"\n    go tool covdata percent -i=\"$PWD/covdata\"\n\nThe same tool can also convert to the old text format:\n\n    go tool covdata textfmt -o cover.out -i=\"$PWD/covdata\"\n\nSee https://go.dev/doc/build-cover","shortMessageHtmlLink":"feat(mockgen): record code coverage for test scripts"}},{"before":"aafb5053eb0b8476481d8ed4933b25fc9640884a","after":null,"ref":"refs/heads/coverage","pushedAt":"2023-12-22T06:01:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"b75a1e61aedebc162b252efe433bf8f81b44735a","after":"da222c75fa61208061495fa315b9c0dc67722d75","ref":"refs/heads/main","pushedAt":"2023-12-22T06:01:23.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): record code coverage for test scripts\n\nPrior to this change, the test scripts (under ./cmd/mockgen) would run\nthe command using go-run, which builds the mockgen binary and then runs\nit.  This meant that no code coverage was collected for these tests.\n\nThis change introduces a custom TestMain function that builds the binary\nwith the -cover option (new in go 1.20) which produces coverage data in\na binary format.  The go-test command can also produce data in the same\nformat when given the -test.gocoverdir option.  When the ./cmd/mockgen\ntests find this option, coverage for the script tests is enabled.  This\nallows us to then combine the coverage from the tests across all\npackages.  At this time, the go-test command doesn't appear to be able\nto do this automatically and the coverage reported is inaccurate.  To\ngenerate the combined coverage use the covdata tool after running\ngo-test:\n\n    mkdir \"$PWD/covdata\"\n    go test -cover ./... -test.gocoverdir=\"$PWD/covdata\"\n    go tool covdata percent -i=\"$PWD/covdata\"\n\nThe same tool can also convert to the old text format:\n\n    go tool covdata textfmt -o cover.out -i=\"$PWD/covdata\"\n\nSee https://go.dev/doc/build-cover","shortMessageHtmlLink":"feat(mockgen): record code coverage for test scripts"}},{"before":"987aedbefdf85ae5d8605eba411297fdde325436","after":"aafb5053eb0b8476481d8ed4933b25fc9640884a","ref":"refs/heads/coverage","pushedAt":"2023-12-22T05:59:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): record code coverage for test scripts\n\nPrior to this change, the test scripts (under ./cmd/mockgen) would run\nthe command using go-run, which builds the mockgen binary and then runs\nit.  This meant that no code coverage was collected for these tests.\n\nThis change introduces a custom TestMain function that builds the binary\nwith the -cover option (new in go 1.20) which produces coverage data in\na binary format.  The go-test command can also produce data in the same\nformat when given the -test.gocoverdir option.  When the ./cmd/mockgen\ntests find this option, coverage for the script tests is enabled.  This\nallows us to then combine the coverage from the tests across all\npackages.  At this time, the go-test command doesn't appear to be able\nto do this automatically and the coverage reported is inaccurate.  To\ngenerate the combined coverage use the covdata tool after running\ngo-test:\n\n    mkdir \"$PWD/covdata\"\n    go test -cover ./... -test.gocoverdir=\"$PWD/covdata\"\n    go tool covdata percent -i=\"$PWD/covdata\"\n\nThe same tool can also convert to the old text format:\n\n    go tool covdata textfmt -o cover.out -i=\"$PWD/covdata\"\n\nSee https://go.dev/doc/build-cover","shortMessageHtmlLink":"feat(mockgen): record code coverage for test scripts"}},{"before":null,"after":"987aedbefdf85ae5d8605eba411297fdde325436","ref":"refs/heads/coverage","pushedAt":"2023-12-22T05:55:21.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): record code coverage for test scripts\n\nPrior to this change, the test scripts (under ./cmd/mockgen) would run\nthe command using go-run, which builds the mockgen binary and then runs\nit.  This meant that no code coverage was collected for these tests.\n\nThis change introduces a custom TestMain function that builds the binary\nwith the -cover option (new in go 1.20) which produces coverage data in\na binary format.  The go-test command can also produce data in the same\nformat when given the -test.gocoverdir option.  When the ./cmd/mockgen\ntests find this option, coverage for the script tests is enabled.  This\nallows us to then combine the coverage from the tests across all\npackages.  At this time, the go-test command doesn't appear to be able\nto do this automatically and the coverage reported is inaccurate.  To\ngenerate the combined coverage use the covdata tool after running\ngo-test:\n\n    mkdir \"$PWD/covdata\"\n    go test -cover ./... -test.gocoverdir=\"$PWD/covdata\"\n    go tool covdata percent -i=\"$PWD/covdata\"\n\nThe same tool can also convert to the old text format:\n\n    go tool covdata textfmt -o cover.out -i=\"$PWD/covdata\"\n\nSee https://go.dev/doc/build-cover","shortMessageHtmlLink":"feat(mockgen): record code coverage for test scripts"}},{"before":"dba698e38f298c1cf5af233f1cfa976931cbc091","after":null,"ref":"refs/heads/custom-funcs","pushedAt":"2023-12-21T22:29:47.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"0e5cd3638dad9b095d791cfa44d9e2ef2cff21be","after":"b75a1e61aedebc162b252efe433bf8f81b44735a","ref":"refs/heads/main","pushedAt":"2023-12-21T22:29:42.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): respect custom function implementations\n\nPrior to this change, a user of mockgen was free to include any function\ndeclarations that they wished, but it was possible that they collided\nwith generated functions, leading to a broken build.\n\nThis change performs a scan of the existing packages for any colliding\nfunction names or functions that already provide the call to\nmock.Expect.  We naively assume that the result of the mock.Expect call\nis returned from the user defined function.  If there is more than one\ncall to a mock.Expect function within a single custom function then we\nignore the custom function and generate functions as per normal.  If\nthere is a function that collides with a generated function name but\ndoes not make a call to a mock.Expect function then the generated\nfunction falls back to a more verbose name.","shortMessageHtmlLink":"feat(mockgen): respect custom function implementations"}},{"before":null,"after":"dba698e38f298c1cf5af233f1cfa976931cbc091","ref":"refs/heads/custom-funcs","pushedAt":"2023-12-19T12:12:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat(mockgen): respect custom function implementations\n\nPrior to this change, a user of mockgen was free to include any function\ndeclarations that they wished, but it was possible that they collided\nwith generated functions, leading to a broken build.\n\nThis change performs a scan of the existing packages for any colliding\nfunction names or functions that already provide the call to\nmock.Expect.  We naively assume that the result of the mock.Expect call\nis returned from the user defined function.  If there is more than one\ncall to a mock.Expect function within a single custom function then we\nignore the custom function and generate functions as per normal.  If\nthere is a function that collides with a generated function name but\ndoes not make a call to a mock.Expect function then the generated\nfunction falls back to a more verbose name.","shortMessageHtmlLink":"feat(mockgen): respect custom function implementations"}},{"before":"de9d7404b11d68e5daaa525aca05424cf315d986","after":null,"ref":"refs/heads/gh-action","pushedAt":"2023-12-19T05:19:51.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"b64f8b0cc8b86ee6824a6285589058d0fcd7dc7e","after":"0e5cd3638dad9b095d791cfa44d9e2ef2cff21be","ref":"refs/heads/main","pushedAt":"2023-12-19T05:19:46.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat: introduce github actions and badges\n\nPrior to this change, there was no automated checks on pull requests and\nwe didn't promote the quality of the project.\n\nThis change introduces github actions to test, vet and report on code\ncoverage.  Also, we link to the go reference page and show badges for\ncode quality and coverage in the README.","shortMessageHtmlLink":"feat: introduce github actions and badges"}},{"before":"adfc2d2e76cda745a534dfba029391dbb3701a9f","after":"de9d7404b11d68e5daaa525aca05424cf315d986","ref":"refs/heads/gh-action","pushedAt":"2023-12-19T05:17:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat: introduce github actions and badges\n\nPrior to this change, there was no automated checks on pull requests and\nwe didn't promote the quality of the project.\n\nThis change introduces github actions to test, vet and report on code\ncoverage.  Also, we link to the go reference page and show badges for\ncode quality and coverage in the README.","shortMessageHtmlLink":"feat: introduce github actions and badges"}},{"before":null,"after":"adfc2d2e76cda745a534dfba029391dbb3701a9f","ref":"refs/heads/gh-action","pushedAt":"2023-12-19T05:09:42.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"feat: introduce github actions and badges\n\nPrior to this change, there was no automated checks on pull requests and\nwe didn't promote the quality of the project.\n\nThis change introduces github actions to test, vet and report on code\ncoverage.  Also, we link to the go reference page and show badges for\ncode quality and coverage in the README.","shortMessageHtmlLink":"feat: introduce github actions and badges"}},{"before":"2ccee95dcc7ddf3e999c9d72b4187785c0ea66e1","after":"b64f8b0cc8b86ee6824a6285589058d0fcd7dc7e","ref":"refs/heads/main","pushedAt":"2023-12-19T05:08:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"fix: remove use of os.Chdir in tests\n\nPrior to this change, TestGenerate was using os.Chdir but this would\nfail intermittently with an error that the txtar files could not be\nfound.  Presumably testscript relies on the working directory to find\nthese files.\n\nThis change introduces the GenerateOption type that can be passed to the\nExecute method.  These follow the functional options pattern and allows\nthe test command to specify the working directory.","shortMessageHtmlLink":"fix: remove use of os.Chdir in tests"}},{"before":"9ce6932467f001f86d8a27c26a28b9455dc39f61","after":null,"ref":"refs/heads/mockgen","pushedAt":"2023-12-19T05:04:50.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"}},{"before":"b67645aa9393eb7c168fcc20ad803652a8b7eef1","after":"2ccee95dcc7ddf3e999c9d72b4187785c0ea66e1","ref":"refs/heads/main","pushedAt":"2023-12-19T05:04:46.000Z","pushType":"pr_merge","commitsCount":7,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"Prior to this change, TestGenerate was using os.Chdir but this would\nfail intermittently with an error that the txtar files could not be\nfound.  Presumably testscript relies on the working directory to find\nthese files.\n\nThis change introduces the GenerateOption type that can be passed to the\nExecute method.  These follow the functional options pattern and allows\nthe test command to specify the working directory.","shortMessageHtmlLink":"Prior to this change, TestGenerate was using os.Chdir but this would"}},{"before":"f0c5a2eeeef29791c39b4385abaa4bcb28d928a4","after":"9ce6932467f001f86d8a27c26a28b9455dc39f61","ref":"refs/heads/mockgen","pushedAt":"2023-12-19T04:32:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"Prior to this change, TestGenerate was using os.Chdir but this would\nfail intermittently with an error that the txtar files could not be\nfound.  Presumably testscript relies on the working directory to find\nthese files.\n\nThis change introduces the GenerateOption type that can be passed to the\nExecute method.  These follow the functional options pattern and allows\nthe test command to specify the working directory.","shortMessageHtmlLink":"Prior to this change, TestGenerate was using os.Chdir but this would"}},{"before":"6932a83e90fc9acafb6d5006d754bd51a9d14336","after":"f0c5a2eeeef29791c39b4385abaa4bcb28d928a4","ref":"refs/heads/mockgen","pushedAt":"2023-12-19T02:34:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"move golden files to a move go tool friendly path","shortMessageHtmlLink":"move golden files to a move go tool friendly path"}},{"before":"2bf7c52006b28ab08aa34acaff5d8340cf57840a","after":"b67645aa9393eb7c168fcc20ad803652a8b7eef1","ref":"refs/heads/main","pushedAt":"2023-12-11T23:23:59.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"doc: clarify delegate implementation\n\nPrior to this change, the implementation of a mock's delegate was\nassumed to be known in the README.\n\nThis change replaces the elipsis with an explanatory comment.","shortMessageHtmlLink":"doc: clarify delegate implementation"}},{"before":"2bf7c52006b28ab08aa34acaff5d8340cf57840a","after":"66b5dbeb9574b2dc64908e32473f93be87ac1785","ref":"refs/heads/doc/mock-behave","pushedAt":"2023-12-11T22:33:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"au-phiware","name":"Corin Lawson","path":"/au-phiware","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/816686?s=80&v=4"},"commit":{"message":"doc: clarify delegate implementation\n\nPrior to this change, the implementation of a mock's delegate was\nassumed to be known in the README.\n\nThis change replaces the elipsis with an explanatory comment.","shortMessageHtmlLink":"doc: clarify delegate implementation"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEHJvImAA","startCursor":null,"endCursor":null}},"title":"Activity · Versent/go-vermock"}