[Doc] Outline workflows for contributors to follow

[annieappflowy]

By @nishp77 :

Hi team, there some issue on github that have the pr's merged but issues still open, could we have the tendency to close issues right after pr?

I would like to ask about how the development process is going about, in terms of issues how they're worked about and is there some specific flow that contributors have? If not could we have some workflow regarding that?

[ChiragKr04]

Something like, as soon as PR is merged the issue will close automatically. Am I getting this right?

[annieappflowy]

@ChiragKr04 yes, I suppose this is a standard way of closing an issue

[IMPranshu]

I think Github Actions does this job. Wait let me look into this matter but it can only be done with the rights to the repo. So I can provide the solution but the AppFlowy team member has to implement it.

[annieappflowy]

I think Github Actions does this job. Wait let me look into this matter but it can only be done with the rights to the repo. So I can provide the solution but the AppFlowy team member has to implement it.

@IMPranshu thanks for offering the help. Please feel free to propose your solutions. We can create a workflow together to get the process kicked off then let the community to fine-tune and improve as we get more feedback

[IMPranshu]

So as I checked and learned from various resources, the issues are automatically closed if we reference the concerned issue in the description of the PR, which is kind of cool, I guess. I am attaching the official GitHub docs explaining this.

I think the AppFlowy team just has to update the PR template to tell the user to include this line issue # number which they are working on so as to streamline the process and we will have automatic issue closing working as a breeze.

Note: I have verified this from various resources and tried it myself it works like a charm. Below I am attaching the links to some of the resources that explain how this automatically works Resource 1(Video) Resource 2(StackOverflow)