Hello everyone, I have added GitHub Actions (see https://github.com/features/actions) to https://github.com/apache/fineract in https://issues.apache.org/jira/browse/FINERACT-829:
New, added just now: https://github.com/apache/fineract/pull/691 let us (you, anyone) comment "/rebase" on any PR to have "git rebase" run on it. You can see it used e.g. on https://github.com/apache/fineract/pull/881. This is very handy for both contributor and committers reviewing PRs to more easily pick up other recently merged changes, instead of having to locally rebase. The remote git branch is of course different than your local one after you use /rebase on your PR. (Note that travis already runs 2 builds, one of a PR "as-is", and another one building the PR merged against develop. So /rebase is mostly useful to RE-run a build after other PRs have been merged, if you need to pick something up. It's not required just to see if there are merge conflicts - GitHub already figures and shows that without /rebase.) Another one we've already had for a while, so more of an FYI/reminder: https://github.com/apache/fineract/pull/692 will automatically comment "This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days." to any PR that has been inactive for 30 days. Initially it will only comment. Another 30 days later it will without any reaction it will automatically close such stale PRs. They will also have a label ("stale"), making it easy to find them again. I think 60 days is a reasonable timeframe for any contributor. <goog_1991841218> https://github.com/apache/fineract/pull/880/files also proposes to add an automated First Interaction welcome message - nice? Best, M. _______________________ Michael Vorburger http://www.vorburger.ch
