starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #625] [IMPROVEMENT]: add github action to limit non public issues #174

New issue

Closed

opened 2026-02-26 18:45:43 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 18:45:43 +03:00

Owner

Originally created by @Dun-sin on GitHub (Nov 3, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/625

Improvement Description

It would be great if there was a github action that automatically locks a new issue so only collabators can comment on it and when the public label is added to it, it automatically unlocks.

Rationale

Would be beneficial for the maintainers to easily keep track of issues instead of going on manual, there won't be any confusion of sorry this isn't a public issue

Proposed Solution

No response

Alternatives (optional)

an alternative solution is to have it open by default with a public label or no label and once the public label is removed the issue is locked with a message saying if anyone has an opinion they can talk about it in the discord server

Additional Context

No response

Please check the boxes that apply to this improvement suggestion.

I have searched the existing issues and improvement suggestions to avoid duplication.
I have provided a clear description of the improvement being suggested.
I have explained the rationale behind this improvement.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.

Originally created by @Dun-sin on GitHub (Nov 3, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/625 ### Improvement Description It would be great if there was a github action that automatically locks a new issue so only collabators can comment on it and when the public label is added to it, it automatically unlocks. ### Rationale Would be beneficial for the maintainers to easily keep track of issues instead of going on manual, there won't be any confusion of `sorry this isn't a public issue` ### Proposed Solution _No response_ ### Alternatives (optional) an alternative solution is to have it open by default with a public label or no label and once the public label is removed the issue is locked with a message saying if anyone has an opinion they can talk about it in the discord server ### Additional Context _No response_ ### Please check the boxes that apply to this improvement suggestion. - [X] I have searched the existing issues and improvement suggestions to avoid duplication. - [X] I have provided a clear description of the improvement being suggested. - [X] I have explained the rationale behind this improvement. - [ ] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation.

kerem

2026-02-26 18:45:43 +03:00

closed this issue
added the
Stale

community
labels

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@TameemAsim commented on GitHub (Nov 3, 2023):

I would love to work on this

@TameemAsim commented on GitHub (Nov 3, 2023): I would love to work on this

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@adithyaakrishna commented on GitHub (Nov 3, 2023):

@Dun-sin Just voicing my thoughts here, if this is implemented, then the whole idea of open-source and meaning behind it kinda doesn't make sense. I mean, some contributors may have a new opinion or perhaps a different approach which can go unnoticed 😶

@adithyaakrishna commented on GitHub (Nov 3, 2023): @Dun-sin Just voicing my thoughts here, if this is implemented, then the whole idea of open-source and meaning behind it kinda doesn't make sense. I mean, some contributors may have a new opinion or perhaps a different approach which can go unnoticed 😶

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@Dun-sin commented on GitHub (Nov 3, 2023):

@Dun-sin Just voicing my thoughts here, if this is implemented, then the whole idea of open-source and meaning behind it kinda doesn't make sense. I mean, some contributors may have a new opinion or perhaps a different approach which can go unnoticed 😶

not exactly, from my understanding of how this project works that's the purpose of what the public and non-public issues serve, it doesn't stop people from voicing opinions because it's not for them, plus you can have your opinions in the PR. But that's just what I understand of what the labels serve.

Summary:
non-public - everyone can voice their opionions
public - only staffs

This is how i have seen it happen

Not everything needs a public opinion as this is a company too😆

@Dun-sin commented on GitHub (Nov 3, 2023): > @Dun-sin Just voicing my thoughts here, if this is implemented, then the whole idea of open-source and meaning behind it kinda doesn't make sense. I mean, some contributors may have a new opinion or perhaps a different approach which can go unnoticed 😶 not exactly, from my understanding of how this project works that's the purpose of what the public and non-public issues serve, it doesn't stop people from voicing opinions because it's not for them, plus you can have your opinions in the PR. But that's just what I understand of what the labels serve. Summary: non-public - everyone can voice their opionions public - only staffs This is how i have seen it happen Not everything needs a public opinion as this is a company too😆

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@catalinpit commented on GitHub (Nov 6, 2023):

Hey @Dun-sin, thanks for the suggestion! I'm not too convinced about this, but let's see what others think, too.

@catalinpit commented on GitHub (Nov 6, 2023): Hey @Dun-sin, thanks for the suggestion! I'm not too convinced about this, but let's see what others think, too.

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@Dun-sin commented on GitHub (Nov 6, 2023):

Hey @Dun-sin, thanks for the suggestion! I'm not too convinced about this, but let's see what others think, too.

you can see a working example here -> https://github.com/EddieHubCommunity/BioDrop/issues/9658

@Dun-sin commented on GitHub (Nov 6, 2023): > Hey @Dun-sin, thanks for the suggestion! I'm not too convinced about this, but let's see what others think, too. you can see a working example here -> https://github.com/EddieHubCommunity/BioDrop/issues/9658

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@catalinpit commented on GitHub (Nov 8, 2023):

Thanks, will check it out!

@catalinpit commented on GitHub (Nov 8, 2023): Thanks, will check it out!

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 8, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

@github-actions[bot] commented on GitHub (Dec 8, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

kerem commented

2026-02-26 18:45:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 16, 2023):

This issue has been closed because of inactivity.

@github-actions[bot] commented on GitHub (Dec 16, 2023): This issue has been closed because of inactivity.

kerem referenced this issue

2026-02-26 18:48:52 +03:00

[PR #174] [MERGED] loading fonts with next/font for no layout shift #774

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#174

No description provided.

Rows
Columns