|
1 | 1 | Proposing a Change |
2 | 2 | ================== |
3 | 3 |
|
| 4 | +.. admonition:: Screencast |
| 5 | + :class: screencast |
| 6 | + |
| 7 | + Do you prefer video tutorials? Check out the `Contributing Back To Symfony`_ |
| 8 | + screencast series. |
| 9 | + |
4 | 10 | A pull request, "PR" for short, is the best way to provide a bug fix or to |
5 | 11 | propose enhancements to Symfony. |
6 | 12 |
|
@@ -101,12 +107,6 @@ Check that the current Tests Pass |
101 | 107 | Now that Symfony is installed, check that all unit tests pass for your |
102 | 108 | environment as explained in the dedicated :doc:`document <tests>`. |
103 | 109 |
|
104 | | -.. tip:: |
105 | | - |
106 | | - If tests are failing, check on `Travis-CI`_ if the same test is |
107 | | - failing there as well. In that case you do not need to be concerned |
108 | | - about the test failing locally. |
109 | | - |
110 | 110 | .. _step-2-work-on-your-patch: |
111 | 111 |
|
112 | 112 | Step 3: Work on your Pull Request |
@@ -246,7 +246,7 @@ in mind the following: |
246 | 246 | as defined in `PSR-1`_ and `PSR-2`_. |
247 | 247 |
|
248 | 248 | A status is posted below the pull request description with a summary |
249 | | - of any problems it detects or any `Travis-CI`_ build failures. |
| 249 | + of any problems it detects or any GitHub Actions build failures. |
250 | 250 |
|
251 | 251 | .. _prepare-your-patch-for-submission: |
252 | 252 |
|
@@ -527,5 +527,5 @@ before merging. |
527 | 527 | .. _`PSR-2`: https://www.php-fig.org/psr/psr-2/ |
528 | 528 | .. _`searching on GitHub`: https://github.com/symfony/symfony/issues?q=+is%3Aopen+ |
529 | 529 | .. _`Symfony Slack`: https://symfony.com/slack-invite |
530 | | -.. _`Travis-CI`: https://travis-ci.org/symfony/symfony |
531 | 530 | .. _`Psalm phar is installed`: https://psalm.dev/docs/running_psalm/installation/ |
| 531 | +.. _`Contributing Back To Symfony`: https://symfonycasts.com/screencast/contributing |
0 commit comments