开源日报第1098期：轻量级的笔记服务：《memos》

开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。

2024年2月7日，开源日报第1098期：
今日推荐开源项目：《memos》
今日推荐英文原文：《a solution to contributors creating multiple issues in open source - need feedback 🤞》

开源项目

今日推荐开源项目：《memos》传送门：项目链接

推荐理由：一个开源的、轻量级的笔记服务，开源且永久免费，仅需几秒钟即可通过Docker进行自托管
🔗 官方文档：usememos.com

英文原文

推荐理由：开源项目中贡献者创建多个issue的问题，并提出了详细的解决方案, 这个解决方案可以自动化处理作者创建多个问题的情况，使得维护者能够更高效地跟踪问题并给予反馈

a solution to contributors creating multiple issues in open source - need feedback 🤞

In some open source projects, contributors make lots of issues with some time between them, making it hard to manage. The more issues there are, the tougher it gets.

Every good open source project or major organization deals with this problem.

In general, contributors start with just one issue at a time. As they contribute more, they are allowed to work on multiple issues because they would have gained the trust of maintainers.

Now, during Hacktoberfest or other open source events.
Most of the contributors create multiple issues even when it's mentioned in the guidelines not to do so.

We faced a lot of problems in tracking if a contributor made several issues because they are human and have the intelligence to bypass the system.

In our situation, there are 3-4 maintainers, and each maintainer assigns the issue whenever they can. So, sometimes when I assign someone, he creates an issue after some gap, and this time another maintainer assigns it.

We cannot go back to check which maintainer is assigning whom.
We can solve it with just 1 person assigning issues, but it is still a problem on how one can remember that anyway. For instance, this is not feasible where issues cross 100 or so.

This creates a major problem for maintainers to track how many contributors have created multiple issues.

As you know, I'm a developer and a very picky one 😀
I solved this myself since there was no existing solution.

The solution

I created handle multiple issues workflow to handle this efficiently and quickly.

With this GitHub workflow, you can automate tasks whenever an author creates multiple issues.

So, you can see the case of LinksHub Issue #2251.

The bot clearly says this.

This helps the maintainers because the issues are linked, and it will get noticed.

Now, I have made it good enough to use it in any organization.

name: Handle Multiple Issues

on:
  issues:
    types:
      - reopened
      - opened
jobs:
  handle-multiple-issues:
    runs-on: ubuntu-latest
    steps:
      - name: Handle Multiple Issues
        uses: Anmol-Baranwal/handle-multiple-issues@v1
        with:
          label: "multiple issues" #default
          close: false  #default
          issueNumber: true  #default is true

Marketplace: github.com/marketplace/actions/handle-multiple-issues

What I did was create options.

These options improve the solution for many end-user cases and can make it ready to use in good open source projects.

You can read about options here. I will explain, even if you don't want to.

use cases with options

You can also filter the issues assigned to the author in that open source project.

You can add your own comment message (even multiline) to the issue. (Can be fully customized)

You can add label/labels based on your preferences.

Optionally, you can also close the issue (previous issues won't be affected), and only the current issue will be closed.

You can ignore this workflow for specific users by using ignore users.

You can directly pass ignoreCollaborators.

These are some of the screenshots that you can see to understand the context better.

There are many more which you can learn more from the readme.

I need serious feedback on this.
Thanks for any help you can provide 😀

What else can be added here?
What can be improved?
Is it good enough to use in any open source project?

Thanks a bunch!

下载开源日报APP：https://openingsource.org/2579/
加入我们：https://openingsource.org/about/join/
关注我们：https://openingsource.org/about/love/