summaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Workaround jruby issuejruby_issueDavid Rodríguez2020-02-021-0/+31
|
* Merge #7574Bundlerbot2020-01-201-10/+11
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7574: Improve PR template r=indirect a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that the current PR template sometimes asks too many questions, and the answers are a bit artificial. ### What was your diagnosis of the problem? My diagnosis was that experience tell me that some questions are too much, and a bit artificial to answer for many PRs. ### What is your fix for the problem, implemented in this PR? My fix is to still let contributors know what kind of information we find valuable, but don't force all questions to be answered. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
| * Add a note about rebuilding documentationdocs/improve_pr_templateDavid Rodríguez2020-01-151-0/+5
| |
| * Hide initial textDavid Rodríguez2020-01-151-0/+2
| | | | | | | | | | So that the author gets the message, but it doesn't appear by default in the PR's body.
| * Squash last three questions into just oneDavid Rodríguez2020-01-151-9/+3
| | | | | | | | | | | | In my experience, for most PRs it is enough to just explain the problem and explain your fix, and most times it's a bit artificial to fill out all 4 questions. So, I'm squashing them.
| * Elaborate a bit on each questionDavid Rodríguez2020-01-151-4/+4
| | | | | | | | | | | | Instead of forcing fixed beginning of the answers, give some more information on what's expected, but leave the section wording completely up to the PR author.
| * Include also developer problems in first questionDavid Rodríguez2020-01-151-1/+1
| |
* | [repo move] Update GitHub URL in .github/config.ymlEllen Marie Dash2020-01-161-1/+1
|/
* Add Windows to bors checksDavid Rodríguez2020-01-071-1/+4
|
* Disallow failuresDavid Rodríguez2020-01-071-1/+0
|
* Split test gem installation to a separate taskDavid Rodríguez2020-01-071-1/+1
| | | | | | | We run into a race condition when testing in parallel when all processors install test gems to their test folder (due to shared gem cache). So I figure we can instead run this setup sequentially beforehand.
* Run specs in parallel to speed things upDavid Rodríguez2020-01-071-1/+1
|
* Migrate Windows CI to Github actionsDavid Rodríguez2020-01-041-0/+34
|
* Fix documents to refer to URLs with httpsTakayuki Nakata2019-08-091-1/+1
|
* Configure Sponsor button on GitHubAndré Arko2019-05-241-0/+1
|
* use '|' to preserve line breaks in welcome messageColby Swandale2018-11-271-1/+1
|
* move welcome message to new welcome botcolby/new-welcome-botColby Swandale2018-11-242-7/+9
|
* delete merged branches automaticallyindirect/delete-merged-branchesAndre Arko2018-10-311-1/+2
|
* wait up to 4 hours for staging pushes to buildAndre Arko2018-09-191-0/+2
|
* tell bors to use Travis to testindirect/homu-to-borsAndre Arko2018-09-191-0/+4
|
* let's see if the other format parsesAndre Arko2018-09-191-1/+3
|
* configure bors instead of homuAndre Arko2018-09-181-0/+1
|
* Fix link to contributing dochmistry2018-03-081-1/+1
|
* Fix typo in pull request templateGrey Baker2017-06-291-1/+1
|
* remove info about running test suite, its redundantcolby/welcome-messageColby Swandale2017-06-221-1/+1
|
* feedback and fixed some clarity issuesColby Swandale2017-06-221-2/+2
|
* add welcome message for PR auto repliesColby Swandale2017-06-221-0/+7
|
* Add a PR templateseg-pr-template-questionsSamuel Giddins2017-06-121-0/+18