Fixed

• The 1.3.1 fix for the ignore --since option accidentally ignored since settings in configuration files. This is now fixed, closing issue 36. Thanks, Lucas Taylor.

Fixed

• When using a URL on the command line, the --since option was ignored. This is now fixed, closing issue 35.

Added

• The since date can now be specified on the command line with --since. This will override any specification in the YAML file.
• The since value can be specified as a specific ISO 8601 date or datetime, closing issue 26.

Added

• Now you can additionally specify digests on the command line to write, which will choose just those digests from the configuration file.

Fixed

• If the config file has no digests: clause, it could be because it's not a dinghy config file at all, so print an error message about it.

Added

• A digest can specify template, a Jinja2 template file to produce the digest. This opens the possibility for other output formats than HTML.

• Nothing has changed, just decided Dinghy was stable enough to call 1.0.0.

Added

• Show releases in the digest. Thanks, Simon de Vlieger.
• A new setting include_bots: true will include pull requests, issues, or comments created by bot users. The default remains False, to exclude them. Closes issue 25.

Added

• Now a CLI command is registered so you can use dinghy as a command instead of python -m dinghy (though that still works).
• You can now specify since: forever to include all activity regardless of when it happened.

Changed

• Search results now always show the repo containing the item.

Fixed

• Comments by deleted GitHub users would cause a crash. This is now fixed (issue 23).

Fixed

• Comments on pull requests were only filtered by their age, not their authors, so bot comments, and comments by "ignored users" were still included. This is now fixed.

Fixed

• The hover tip for icons on pull requests and issues has text in the same order as the icons, making them easier to understand.

Fixed

• Add an HTML <meta> tag to ensure content is properly decoded as UTF-8. Fixes issue 12. Thanks, Bill Mill.

Fixed

• On Windows, an alarming but harmless error would appear when finishing. This is now fixed, closing issue 9. Thanks, Carlton Gibson.

Removed

• Removed the deprecated "pull_requests" setting.

Added

• The api_root setting lets GitHub Enterprise users control the GraphQL endpoint to use.

Changed

• Adapt to the 2022-06-23 GitHub issues update, using the ProjectsV2 API instead of the ProjectsNext API.

Added

• The title option can be used on individual digests to add text to the title of the report. Thanks, Doug Hellmann.

Fixed

• Closed issues now distinguish between "completed" and "not planned".

Added

• HTML escaping is applied to the text pulled from GitHub (oops!)
• Emojis are displayed as emojis rather than as text.

Fixed

• GitHub sometimes responds with "502 Bad Gateway". Pause and retry if that happens.

Fixed

• Corrected a packaging mistake (missing Changelog entry).

Added

• Added a --version option.

Fixed

• Pull requests with many reviews would skip some reviews. Now all pull request data is fully retrieved.
• On large digests, GitHub sometimes returns 403 as a rate limit. Retry when this happens to finish the queries.

Added

• Items can have options. Organization projects have a home_repo option so that issues from other repos will get an indication of the other repo.
• Organizatons can be searched for pull requests.
• If dinghy hits a GraphQL API rate limit, it will sleep until the limit is reset.
• Don't report on activity by bot users. The bot setting can be used to list user accounts that should be considered bots.