Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

remove reference to Travis CI (no longer free)#20938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
javiereguiluz merged 1 commit intosymfony:6.4fromtacman:patch-29
May 7, 2025
Merged
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletionsbundles/best_practices.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
Best Practices for Reusable Bundles

Check failure on line 1 in bundles/best_practices.rst

View workflow job for this annotation

GitHub Actions/ Lint (DOCtor-RST)

The following link definitions aren't used anymore and should be removed: "Travis CI"
===================================

This article is all about how to structure your **reusable bundles** to be
Expand DownExpand Up@@ -195,8 +195,7 @@

Testing bundle code continuously, including all its commits and pull requests,
is a good practice called Continuous Integration. There are several services
providing this feature for free for open source projects, like `GitHub Actions`_
and `Travis CI`_.
providing this feature for free for open source projects, like `GitHub Actions`_.

A bundle should at least test:

Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp