Maybe a bit late, but maybe a repository could be create just for issues.
Code repositories would just have discussion on pull requests.
This might also make managing and filtering subscriptions easier.
On 12/8/22 14:36, Antoine Pitrou wrote:
I'm not sure it makes sense to file website issues
I think it makes sense to file issues where they are relevant. Issues that
are concerned with changes to parts of the website that live in
apache/arrow-site (the markdown content, jekyll templates and deploy
workflows) should be filled as GH issues in apache/arrow-site. And issues
concerning the do
I'm not sure it makes sense to file website issues to a different repo
than documentation issues.
Regards
Antoine.
Le 08/12/2022 à 11:50, Joris Van den Bossche a écrit :
On Tue, 6 Dec 2022 at 08:41, Benson Muite wrote:
For sure the exact workflows will still be further refined while
On Tue, 6 Dec 2022 at 08:41, Benson Muite wrote:
>
>
> > For sure the exact workflows will still be further refined while starting
> > to use this. And if there are things missing or unclear in the current
> > practices around how to handle GitHub issues or any other feedback or
> > ideas, this th
For sure the exact workflows will still be further refined while starting
to use this. And if there are things missing or unclear in the current
practices around how to handle GitHub issues or any other feedback or
ideas, this thread is yours!
Maybe helpful to also update website bot:
https://
We should define a unified syntax for all comment-based actions, because
right now it's a hodgepodge of mixed conventions.
Le 02/12/2022 à 13:52, Jacob Wujciak a écrit :
Hello Everyone,
A quick update, anyone (regardless of committer status) can now self-assign
issues by commenting "take"
Hello Everyone,
A quick update, anyone (regardless of committer status) can now self-assign
issues by commenting "take" on the issue.
The PR with examples: https://github.com/apache/arrow/pull/14785
On Wed, Nov 30, 2022 at 4:04 PM Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:
> Hi
Hi all,
There is a separate vote thread about already using GitHub issues for all
new issues (and in practice users also are already doing that, since new
JIRA signup has been disabled). And so to prepare for this, there has been
some ongoing work to update our workflows to handle GitHub issues (b
