kiszk commented on a change in pull request #286:
URL: https://github.com/apache/spark-website/pull/286#discussion_r475097318
##########
File path: developer-tools.md
##########
@@ -228,6 +228,25 @@ Getting logs from the pods and containers directly is an
exercise left to the re
Kubernetes, and more importantly, minikube have rapid release cycles, and
point releases have been found to be buggy and/or break older and existing
functionality. If you are having trouble getting tests to pass on Jenkins, but
locally things work, don't hesitate to file a Jira issue.
+<h3>Running tests in your forked repository using GitHub Actions</h3>
+
+GitHub Actions is a functionality within GitHub that enables continuous
integration and a wide range of automation.
+We have already started uing some action scripts and one of them is to run
tests for Pull Requests.
+If you are planning to create a new Pull Reques, it is important to check if
tests can pass on your branch before creating it.
+This is because our GitHub Acrions script automatically run tests for your
Pull Request/following commits and
+this can burden our limited resources of GitHub Actions.
+
+Our script enables you to run tests for a branch in your forked repository.
+Let's say that you have a branch named "your_branch" for a Pull Request.
+To run tests on "your_branch" and check test reuslts:
Review comment:
nit: `reuslts` -> `results`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org
