mirrors
/
vaadin-framework
mirror of https://github.com/vaadin/framework.git
Watch 1
Star 0
Fork 0
Code Issues 0 Releases 328 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
18618 Commits
114 Branches
Tree: c8b1d0daae
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'c8b1d0daae'
${ noResults }
vaadin-framework/.github/stale.yml

stale.yml 1.9KB
Raw Blame History

123456789101112131415161718192021222324252627 
  1. daysUntilStale: 150

  2. daysUntilClose: 900

  3. exemptLabels:

  4.  - BFP

  5.  - Pinned

  6.  - enhancement

  7. staleLabel: Stale

  8. only: issues

  9. # Comment to post when closing a stale Issue or Pull Request.

  10. closeComment: >

  11.   The issue was automatically closed due to inactivity. If you found some new details to it or started working on it, comment on the issue so that maintainers can re-open it.

  12. 

  13. markComment: |

  14.   Hello there!

  15.   

  16.   We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

  17.   

  18.   There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  19.   

  20.    * Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.

  21.    * Provide more details how to reproduce the issue.

  22.    * Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.

  23.    * Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.

  24.    * Try [fixing the issue yourself](https://github.com/vaadin/framework/blob/master/CONTRIBUTING.md) and [create a pull request](https://help.github.com/categories/collaborating-with-issues-and-pull-requests/) that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.

  25.    * If the issue is clearly a bug, use the [Warranty](https://vaadin.com/pricing) in your Vaadin subscription to raise its priority.

  26.   

  27.   Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!