This is an automated email from the ASF dual-hosted git repository.

fanningpj pushed a commit to branch main
in repository 
https://gitbox.apache.org/repos/asf/incubator-pekko-platform-guide.git


The following commit(s) were added to refs/heads/main by this push:
     new ad9b3a15 Update CONTRIBUTING.md
ad9b3a15 is described below

commit ad9b3a152dabcc5d19fefecc9aec78a4aace38cd
Author: PJ Fanning <[email protected]>
AuthorDate: Wed Dec 27 19:50:00 2023 +0100

    Update CONTRIBUTING.md
---
 CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9d2bf046..151886eb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,7 +12,7 @@ You may also check out the [Pekko dev mailing 
list](https://lists.apache.org/lis
 
 # Antora-based Pekko Documentation
 
-This folder contains the sources for parts of the [Akka Platform Guide web 
site](https://developer.lightbend.com/docs/akka-platform-guide).
+This folder contains the sources for parts of future Pekko Platform Guide web 
site. The equivalent [Akka Platform Guide web 
site](https://developer.lightbend.com/docs/akka-guide/) should be a useful 
guide until we are complete.
 
 This folder is structured as follows:
 - The root directory contains the `Makefile` for the documentation generation 
process.
@@ -74,5 +74,5 @@ It's often easiest to make changes to the example in the full 
example (last part
 propagate those changes backwards with `scripts/copy-identical-files.sh` and 
manual edits of non-identical
 files. IntelliJ has a good diff tool for propagating changes between files and 
folders.
 
-PR validation in Travis will run the `scripts/copy-identical-files.sh` and 
fail the build if expected identical
+PR validation in GitHub Actions CI will run the 
`scripts/copy-identical-files.sh` and fail the build if expected identical
 files are different.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to