{"id":13600547,"url":"https://github.com/flows-network/follow-up-github-issue","last_synced_at":"2025-04-11T00:31:26.081Z","repository":{"id":158107872,"uuid":"625074031","full_name":"flows-network/follow-up-github-issue","owner":"flows-network","description":null,"archived":false,"fork":false,"pushed_at":"2023-06-25T09:05:54.000Z","size":32,"stargazers_count":0,"open_issues_count":0,"forks_count":2,"subscribers_count":2,"default_branch":"main","last_synced_at":"2024-11-07T03:41:45.463Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Rust","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/flows-network.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2023-04-08T02:02:17.000Z","updated_at":"2023-06-08T10:19:05.000Z","dependencies_parsed_at":"2024-03-30T23:32:20.213Z","dependency_job_id":"2f0d2098-2149-43fd-a547-edb4d087c020","html_url":"https://github.com/flows-network/follow-up-github-issue","commit_stats":null,"previous_names":[],"tags_count":0,"template":true,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/flows-network%2Ffollow-up-github-issue","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/flows-network%2Ffollow-up-github-issue/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/flows-network%2Ffollow-up-github-issue/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/flows-network%2Ffollow-up-github-issue/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/flows-network","download_url":"https://codeload.github.com/flows-network/follow-up-github-issue/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248322267,"owners_count":21084334,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-01T18:00:41.758Z","updated_at":"2025-04-11T00:31:25.744Z","avatar_url":"https://github.com/flows-network.png","language":"Rust","funding_links":[],"categories":["GitHub"],"sub_categories":[],"readme":"# Unanswered Issue Reminder\n\n[Deploy this bot on your GitHub repo via flows.network](#deploy-your-own-unanswered-issues-alert-bot), and you will get a Slack bot that reminds you when an issue raised to your GitHub repo hasn't been responded to in a certain number of days. You can set how many days freely. It helps DevRel and maintainers to track the progress of GitHub issues.\n\n\u003cimg width=\"435\" alt=\"image\" src=\"https://github.com/flows-network/follow-up-github-issue/assets/45785633/60725355-b199-4171-95dd-8f3e6c3a9417\"\u003e\n\n\nThis is a simple example of how flows.network works: When the GitHub issue doesn't get any response in 2 days, you will receive a Slack message.\n\n## Deploy your own unanswered issues alert bot\n\n1. Load the [unanswered GitHub issues reminder](https://flows.network/flow/createByTemplate/unanswered-issue-reminder) template.\n2. Configure and authorize your Slack access\n3. Configure the bot to access a specified GitHub repo\n\n### 0 Prerequisites\n\nYou will need to sign into [flows.network](https://flows.network/) from your GitHub account. It is free.\n\n### 1 Load the template for monitoring the unanswered GitHub issues\n\n[**Just click here**](https://flows.network/flow/createByTemplate/unanswered-issue-reminder)\n\n[\u003cimg width=\"450\" alt=\"image\" src=\"https://github.com/flows-network/follow-up-github-issue/assets/45785633/0768399f-8236-45d1-868b-2128378a8a58\"\u003e](https://github.com/flows-network/follow-up-github-issue/assets/45785633/0768399f-8236-45d1-868b-2128378a8a58)\n\n\nReview the `n_days` variable. This number decides how long to trigger this flow. The number here must be a positive integer greater than or equal to 1. \n\nClick on the **Create and Build** button.\n\n### 2 Configure the bot to access your Slack\n\nNext, you will tell the bot which Slack channel you want your alert messages to be sent to.\n\n* `slack_channel`:\nenter the name of your Slack organization where you want to deploy the bot. Case sensitive.\n\n* `slack_workspace`:\nenter the name of the Slack channel where you want to deploy the bot. Case sensitive.\n\nEnter your Slack workspace and channel respectively in the red boxes below.\n\n[\u003cimg width=\"450\" alt=\"image\" src=\"https://github.com/flows-network/github-star-slack-messenger/assets/37167103/7ec3b6ce-c180-4fec-8546-2dddfb9f3d85\"\u003e](https://github.com/flows-network/github-star-slack-messenger/assets/37167103/7ec3b6ce-c180-4fec-8546-2dddfb9f3d85)\n\n\nNext, let's grant flows.network to access the Slack channel you just entered. The Slack channel must be public.\n\nClick the \"Connect/+ Add new authentication\" button to authenticate your Slack account. You'll be redirected to a new page where you must grant [flows.network](https://flows.network/) permission to install the `flows-network` bot on your workspace. This workspace is the one you entered into the `slack_workspace` above.\n\n\u003e If you have authenticated the Slack access before, you can see the purple Connect button turns gray Connected button. Just ignore this step and continue the next steps.\n\n### 3 Configure the bot to access GitHub\n\nNext, you will tell the bot which GitHub repo's issues need to monitor.\n\n* `github_owner`: enter the name of the GitHub org for the repo *you want to deploy the 🤖 on*.\n* `github_repo` : enter the name of GitHub repo *you want to deploy the 🤖 on*.\n\nClick on the **Connect** or **+ Add new authentication** button to give the function access to the GitHub repo to deploy the 🤖. You'll be redirected to a new page where you must grant [flows.network](https://flows.network/) permission to the repo.\n\n[\u003cimg width=\"450\" alt=\"image\" src=\"https://github.com/flows-network/github-fork-alert-slack/assets/45785633/869e4a84-76b4-4613-b8e3-d75b94c82f50\"\u003e](https://github.com/flows-network/github-fork-alert-slack/assets/45785633/869e4a84-76b4-4613-b8e3-d75b94c82f50)\n\n\n\u003e If you have authenticated the GitHub access before, you can see the purple Connect button turns gray Connected button. Just ignore this step and click the Check button.\n\n### 4. Click the Deploy button to deploy your function.\n\nAfter that, click the Check button to see your flow details. As soon as the flow function's status becomes `ready` and the flow's status became `running`, you will get a Slack message every time the GitHub issue isn't responded to in time.\n\n\n\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fflows-network%2Ffollow-up-github-issue","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fflows-network%2Ffollow-up-github-issue","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fflows-network%2Ffollow-up-github-issue/lists"}