You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2022. It is now read-only.
One of them is that using Github Actions to add PRs to boards we miss all PRs from first contributors as they require approval to run actions. Also, Github doesn't merge an issue and a PR so there is a duplication (we archive excessive PRs ATM).
As it's a good practice to have an issue for every PR for proper analysis and discussion we might consider removing PR tracking from our boards at all managing them in the linked PRs issue's column.
The text was updated successfully, but these errors were encountered:
we have many PRs from our side not covered by any issue
we also sometime get collaborator PRs when they don't create any issue
the idea that we get notified about everything on our board feels good to me
As it's don't really hard for me to archive duplicate PRs I think keeping PRs on the board still will bring more additional value rather removing them save addition time.
I'm closing it for now, please re-open if you think we need to consider/discuss it more
Overview
Currently, Github Projects Beta has some limitations described in frictionlessdata/frictionlessdata.io#751
One of them is that using Github Actions to add PRs to boards we miss all PRs from first contributors as they require approval to run actions. Also, Github doesn't merge an issue and a PR so there is a duplication (we archive excessive PRs ATM).
As it's a good practice to have an issue for every PR for proper analysis and discussion we might consider removing PR tracking from our boards at all managing them in the linked PRs issue's column.
The text was updated successfully, but these errors were encountered: