| Option | Description |
plugin_followup
|
Enable followup plugin
![]() |
type: boolean
default: no
|
plugin_followup_sections
|
Displayed sections
repositories: overall status of issues and pull requests on your repositories
user: overall status of issues and pull requests you have created on GitHub
![]() |
type: array
(comma-separated)
default: repositories
allowed values: |
plugin_followup_indepth
|
Indepth analysis
![]() |
đ Web instances must configure settings.json:
- metrics.api.github.overuse
type: boolean
default: no
|
plugin_followup_archived
|
Include archived repositories
![]() |
type: boolean
default: yes
|
## đ `indepth` mode
The `plugin_followup_indepth` option collects additional stats to differentiate issues and pull requests opened by maintainers and users.
It helps knowing whether repositories are also maintained by other users and give an overall health status of repositories.
> â ī¸ This mode will try to list users with push access to know who are the maintainers in order to place issues in the correct category, which requires a `repo` scope. If not available, it will consider that only the owner is a maintainer.
## âšī¸ Examples workflows
```yaml
name: Opened on user's repositories
uses: lowlighter/metrics@latest
with:
filename: metrics.plugin.followup.svg
token: ${{ secrets.METRICS_TOKEN }}
base: ""
plugin_followup: yes
```
```yaml
name: Opened by user
uses: lowlighter/metrics@latest
with:
filename: metrics.plugin.followup.user.svg
token: ${{ secrets.METRICS_TOKEN }}
base: ""
plugin_followup: yes
plugin_followup_sections: user
```
```yaml
name: Indepth analysis
uses: lowlighter/metrics@latest
with:
filename: metrics.plugin.followup.indepth.svg
token: ${{ secrets.METRICS_TOKEN }}
base: ""
plugin_followup: yes
plugin_followup_indepth: yes
```
```yaml
name: Exclude Archived
uses: lowlighter/metrics@latest
with:
filename: metrics.plugin.followup.archived.svg
token: ${{ secrets.METRICS_TOKEN }}
base: ""
plugin_followup: yes
plugin_followup_archived: no
```