DEV Community: Param

dvibe - share Repo updates to slack / discord

Param — Tue, 23 May 2023 02:51:08 +0000

What I built

A github action, which takes the webhook link as parameter, and publish the current repositories data to slack channel, using webhook

Category Submission:

New github action.

App Link

https://github.com/marketplace/actions/github-repo-reports

Screenshots

Description

Takes the webhook url as parameter, and use git api & chats.io api, and generate a image based report to slack.

Link to Source Code

https://github.com/parama4u/dvibe

Permissive License

MIT

Background (What made you decide to build this particular app? What inspired you?)

I am in IT world for 15+ years, half in big orgs, and other half in startups, its always a issue,where to see a granular status report of a Repo. Github provoids off-the-shelf, other paid tools do similar.

The issue is when Micro-service-architecture followed, and we have 20+ micro services, its hard to check one by one on repo.
Its also hard to integrate the same to new micro-services, and manage accesses.

So simplifying issue and solution, making it gitaction, set that a cron based report, and its on code, new repos can simply copy paste the same action, with dev - review - merge route.

How I built it (How did you utilize GitHub Actions or GitHub Codespaces? Did you learn something new along the way? Pick up a new skill?)

Used local environment, and github actions. I am publishing a github action on my own for the first time, was spending 70% time on github actions documentation page.

Additional Resources/Info

Planning to add more graphs, will continue the project, after the hackathon too.

The 10 Day Ship : Day 3/4 - [NullPointer exception] Fixed #GitHubHack23

Param — Tue, 16 May 2023 16:03:53 +0000

Here we are , in addition to day2's research, i was looking for ways to do the report I wanted to build.

Found one.

Graph is not supported in Slack.

Found another one.

I need a slack channel to build it.

Created one.

Now processor working fine.

Sample report is generated.

So, from here onwwards, goes up 🚀

The 10 Day Ship : Day 2 - Switching gears #GitHubHack23

Param — Sun, 14 May 2023 20:13:54 +0000

The idea on Day1 was to build a github action, which will update the jira statuses automatically. Yes, its a pain point on my day job.

To Update (To Do -> In progress -> Done)
To update back, (well, when i sent a PR for review, reviwer asked for changes, The PR is not in review any more. it should be back to in progress? )
Change between Merge vs Deployed

Just realized, there are already github actions, and i cannot expose or share the work for my day-job in public. So switching gear.

New Idea? Do summaries for PRs per repo to Slack. A Daily job, do a report, with Open PRs, expecting next step from which person, a summary.

May be just top10 PRs? may be least 10? need to think more while building or iterating.

lets see.

The 10 Day Ship : Day 1 - Intro #GitHubHack23

Param — Sat, 13 May 2023 02:16:18 +0000

Seems I am late to the party. May23 is the submission date, and got to know about the hackathon just now. I have an idea. actually, a workplace issue,i want to solve.

So, the journey will be recorded here, this is a daily journal, i will write daily to share updates. Yeah, added that as a series.

Been in corporate grind first 8 years, and last 8 years in startup. Just a wander kid to build-in-public and indie hacker grind on 2023.

The idea for the hackathon is just my long-pending issue I want to solve or solved in other ways. Duplicate updates about my progress.

I code.
I build.
I merge.
I deploy.

All the above are fun. What is not fun? updating jira, slack and other stuff just to make others look at my progress. I solved it in other ways in the past. Now want to build a github action, do that not-fun part for me.

Have some questions. asked in the help thread. Lets see where it goes.