bewuethr / slack-analyzer

An action to analyze a Slack workspace over time

Hi there 👋

It's Wednesday! I might be watching YouTube videos about relay computers.

Weather in Toronto: partly cloudy, at +18°C.

slack-analyzer's Issues

Update documentation

• Add example graph
• Add example table for current employees
• Add example table for all tenures
• Add example Telegram diff message
• Add example Telegram graph message
• Add details about corrections.csv
• Add some implementation description
• Add instructions to get Telegram tokens

Duration boxplot tries to access wrong column

Should be 6 here:

slack-analyzer/action.yml

Lines 129 to 131 in de9e7dc

	prettyprintduration < data/tenures.tsv \
	| cut --fields=5 \
	| gnuplot '${{ github.action_path }}/scripts/durationboxplot.gpi'

Use symlink to point to latest diff instead of updating README

Add result table with only current employees

Show separate boxplots for all and current employees

Refactor tenureupdate

Use old status and print result / unset variables just once

Consider case where tenures.tsv doesn't exist yet

Profile name change shouldn't trigger sending tenure graph

Move diffs into subdirectory

Convert to an action

Make it clear that stats and boxplot are for all tenures

Diff message is sent for same diff

See this run – the git status after committing the README must have been non-empty and ended up sending the diff from the previous run.

The durations Markdown file maybe?

Add automation to create a release when tagging

Some way to show who overlapped with whom

Add stats

Things such as

• Sort by tenure length
• Median tenure, percentiles, histogram?

Fix diff format

Do I want "unified"?

Users deleted in corrections shouldn't be looked up

Because they never make it into tenures.tsv, they are considered as fresh every time and trigger Slack API calls.

Be even more quiet

Fix `--quiet` in `apt-get install`

Fix indentation

This isn't right:

slack-analyzer/scripts/slacktenure

Lines 114 to 115 in c669487

	}
	}' "$infile"

Colourize log messages for better visibility

Add a tool to simplify adding corrections

Number of current employees doesn't match between table and graph

Possibly related to #53?

Count fresh users as active

This would get around the problem of new employees who don't post for a while. The start date could be the timestamp of when they were first registered.

Handle reactivations

Example: U016GJL1R4Y left and came back, but still shows as "alum"

Graph tweaks

• More horizontal lines
• Drop numbers on bars
• Label right y-axis

Send Telegram message when change happens

See Telegram Bots documentation.

Handle rate limiting smarter

Instead of waiting for 3 seconds after each Slack call, inspect the response, and if it's an HTTP 429 Too Many Requests error, wait for the time indicated by the Retry-After header; see Slack Rate Limits documentation.

Automate assigning a label to a PR when created and linked to an issue

Options:

• manually parse the PR body to find the reference to the issue, doesn't look like the API provides it; doesn't catch manually linked issues
• the timeline of an issue shows when it was cross-referenced by a PR; does linking trigger an edited event on the issue?

Set up a release notes template

Add secret scanning when bumping super-linter

See https://github.com/github/super-linter/releases/tag/v4.8.0

Add reusable workflows

Not here, probably in a separate repo. See https://docs.github.com/en/actions/learn-github-actions/reusing-workflows

Don't mention `corrections.csv` if there isn't one

Upgrade super-linter

Double quotes in tenures.tsv break TSV rendering

Allow for manual corrections

• Override start or end date
• Combine accounts for multiple users who were the same person
• Exclude full users who weren't actually employees

Get rid of intermediate tenures TSV

Instead of creating a new file and diffing, overwrite the existing one and use git diff to compare to the previous version.

Integrate Telegram action

Take advantage of the new uses: keyword for composite actions and make the use of the Telegram action transparent.

Look into automated release notes

https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

• #70
• #71
• #72

Use grouping to make logs less noisy

See https://docs.github.com/en/actions/learn-github-actions/workflow-commands-for-github-actions#grouping-log-lines

Add labels to outliers in boxplot

Or maybe switch to a bee swarm plot!

Use "if" statements for composite action

See https://github.blog/changelog/2021-11-09-github-actions-conditional-execution-of-steps-in-actions/

Group diffs into subdirectories

Add link to most recent diff to bottom of tenures.md

Or top of README

Add link to most recent diff to Telegram message

Trim leading and trailing spaces for "by duration" table

Something like product with a trailing blank becomes

*product *

resulting in

*product *

Replacing double quotes with single quotes makes changed user show up in diff every day

Indicate who's not at the company any longer in the durations table

Maybe italics for former employees?

Don't install gnuplot if not required

Move files into subdirectories to declutter