Skip to content

Make Github actions/checkout CI tests merge into master HEAD, instead of into the master past #329

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Open
alfsb wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Make Github actions/checkout CI tests merge into master HEAD, instead of into the master past #329

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
24 changes: 16 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,18 @@
This repository contains the base source files and tools for converting
PHP's documentation, written in DocBook XML, into various presentation
formats like HTML and RTF.

Documentation for the tools used for building the PHP documentation and
how to contribute to the documentation and translations can be found in
[the `docs` directory](docs/README.md).
This is a test only branch/PR, with the objective of studying ways to make Github CIs to *not* ignore posterior changes on main/master.

If you just want to read the documentation for PHP, look at:
https://www.php.net/docs.php
DO NOT MERGE.

The doc-base history before branching:

```
commit c45b8a3d6085b8b18a0938e5ac571403da5541ed master HEAD
commit 982980a58b8b05b5cbdb832aa426a5b29df77a46
commit 9391318e46e6fdd09721a9f5e3553089e4382009 <- branch from here
commit 4555190558990db31583a997bfa010d1823d1cae
commit d9e120747d082ae07c1e924b4f85e8bede7f680a older
```

The branching was intentionally done in the past of master to test a secondary question: future commits on master HEAD changes anything in GH actions/checkout?

Changed README.md, added, committed and then PR opened.