Skip to content

Update docs explaining the stale bot usage#4523

Merged
manishgarg1 merged 3 commits intomicrosoft:masterfrom
manishgarg1:manishga/staleBotUpdates
Apr 11, 2018
Merged

Update docs explaining the stale bot usage#4523
manishgarg1 merged 3 commits intomicrosoft:masterfrom
manishgarg1:manishga/staleBotUpdates

Conversation

@manishgarg1
Copy link
Copy Markdown
Collaborator

Description of changes

Updated the documentation with stale bot usage and some other minor fixes.

Copy link
Copy Markdown
Collaborator

@oengusmacinog-zz oengusmacinog-zz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

document.body.firstChild
);
```
**[⬆ back to top](#Contents)**
Copy link
Copy Markdown
Contributor

@jordandrako jordandrako Apr 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you remove all the links to the ToC? #Resolved

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They were not working on GitHub. Will figure later why but for now they were creating noise and no value.


In reply to: 180925584 [](ancestors = 180925584)

Copy link
Copy Markdown
Collaborator

@oengusmacinog-zz oengusmacinog-zz Apr 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was assuming @manishgarg1 decided against them. Looked like he added them the other day. #Resolved

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, they were just not working. So I am yanking them out. Will fix them later in a way that they are funcitonal :)


In reply to: 180927395 [](ancestors = 180927395)

FAQ.md Outdated

Stale-bot is versatile and has exemption labels, projects, and milestones. As of right now any issues marked 'Priority 0', 'Priority 1', 'Needs: discussion', and 'Needs: revisit' will never be marked stale.

We ask everyone to not abuse these. This cleanup is for better organization of the Fabric React project with the goal to increase visibility and response time on bugs and feature requests and organizing the issues is key to this endeavor. If there is a more semantic label to express, why your issue needs to stick around for multiple months please contact Michael Angotti (v-micang@microsoft.com) so he can factor that into the organization. No newline at end of file
Copy link
Copy Markdown
Member

@Jahnp Jahnp Apr 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want personal contact info on GitHub? I'd think we'd want to channel this through an issue first. Unless you're comfortable with this, @michaelangotti ;) #Resolved

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed


In reply to: 180925951 [](ancestors = 180925951)

@manishgarg1 manishgarg1 merged commit ee4394f into microsoft:master Apr 11, 2018
@microsoft microsoft locked as resolved and limited conversation to collaborators Aug 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants