Update CI-related docs to current practices

Author: ctrueden

_pages/develop/appveyor.md

@@ -3,11 +3,8 @@ title: AppVeyor
 section: Extend:Development:Tools
 ---
 
-[AppVeyor](https://ci.appveyor.com/) is a tool for [continuous integration](/develop/ci) on [Windows](/platforms/windows) platforms. It is very useful for automating builds, deployment and other tasks.
-
+{% include notice icon="note" content="SciJava projects now use Github Actions for CI. See the [GitHub Actions](/develop/github-actions) page for configuration instructions." %}
 
-# Services
-
-Most [SciJava](/libs/scijava)-based project builds use [GitHub Actions](/develop/github-actions). However, some Windows-specific builds use AppVeyor.
+[AppVeyor](https://ci.appveyor.com/) is a tool for [continuous integration](/develop/ci) on [Windows](/platforms/windows) platforms. It is very useful for automating builds, deployment and other tasks.
 
-See e.g. the [ImageJ Launcher](https://ci.appveyor.com/project/scijava/imagej-launcher) build.
+Some [SciJava](/libs/scijava)-based projects used AppVeyor for Windows-specific portions of their builds, particularly in tandem with [Travis CI](/develop/travis) during the 2017-2021 era.

_pages/develop/github-actions.md

@@ -11,7 +11,7 @@ section: Extend:Development:Tools
 
 -   Perform builds of SciJava projects. Github Actions deploy `SNAPSHOT` builds to the [SciJava Maven repository](https://maven.scijava.org/) in response to pushes to each code repository's `main` branch. So any downstream projects depending on a version of `LATEST` for a given component will match the last successful Github build—i.e., the latest code on `main`.
 -   Run each project's associated {% include wikipedia title='Unit testing' text='unit tests'%}. Github Actions is instrumental in early detection of new bugs introduced to the codebase.
--   Perform [releases](/develop/releasing) of [SciJava](/libs/scijava) projects. Github Actions deploys release builds to the appropriate Maven repository—typically either the SciJava Maven repository or [OSS Sonatype](https://oss.sonatype.org/).
+-   Perform [releases](/develop/releasing) of [SciJava](/libs/scijava) projects. Github Actions deploys release builds to the appropriate Maven repository—typically either the SciJava Maven repository or [Maven Central via the Central Publisher Portal](https://central.sonatype.org/publish/publish-portal-guide/).
 -   Keep the [javadoc](/develop/source#javadocs) site updated.
 -   Keep other web resources updated.
 
@@ -26,16 +26,11 @@ Deploying your library to a [Maven](/develop/maven) repository makes it availabl
 
 ## Instructions
 
--   In order to add Github CI support to a repository, the secrets are needed: A) for deploying to Maven repositories; and B) in the case of deploying to OSS Sonatype, for GPG signing of artifacts. 
+-   In order to add Github CI support to a repository, the secrets are needed: A) for deploying to Maven repositories; and B) in the case of deploying to Maven Central, for GPG signing of artifacts. 
 -   If the secrets have been added to your organization, and you have push access to the relevant repository on GitHub, you can use the [github-actionify.sh script](https://github.com/scijava/scijava-scripts/blob/-/github-actionify.sh) with the `-f` flag to perform the needed operations. 
--   The github-actionify script will return '[ERROR] Dirty working copy' if you have uncommited changes. If you get this error, check the status of the repository with `git status` and then run `github-actionify -f` again.
+-   The github-actionify script will return `[ERROR] Dirty working copy` if you have uncommited changes. If you get this error, check the status of the repository with `git status` and then run `github-actionify -f` again.
 -   If you need help, please ask [on the Image.sc Forum](https://forum.image.sc/) in the Development category, or in the [SciJava stream](https://imagesc.zulipchat.com/#narrow/channel/327237-SciJava) on the Image.sc Zulip.
 
-## Configuration of JavaFX builds
-
--   The workflows configured by the [github-actionify.sh script](https://github.com/scijava/scijava-scripts/blob/-/github-actionify.sh) do not include JavaFX. 
--   To add support for JavaFX, edit the files contained in the folder `.github/workflows/` to match those found in other SciJava projects that depend on JavaFX, e.g. [FilamentDetector](https://github.com/fiji/FilamentDetector).
-
 ## Testing things which cannot run headless
 
 If your tests require a display (i.e.: they do not pass when run [headless](/learn/headless)), you will get errors during the build process such as: 
@@ -44,7 +39,7 @@ If your tests require a display (i.e.: they do not pass when run [headless](/lea
      Error:  myTest  Time elapsed: 0.097 s  <<< ERROR!
 
 You can fix this using [Xvfb](/learn/headless#xvfb-virtual-desktop) as follows.
-In your repository there is a file `.github/workflows/build-main.yml`.
+In your repository there is a file `.github/workflows/build.yml`.
 In this file there should be some lines that read:
 
     - name: Set up CI environment

_pages/develop/travis.md

@@ -3,7 +3,7 @@ title: Travis CI
 section: Extend:Development:Tools
 ---
 
-{% include notice icon="note" content="SciJava [CI](/develop/ci) has [migrated from Travis CI to Github Actions](https://forum.image.sc/t/scijava-ci-migration-from-travis-ci-to-github-actions/57573). See the [GitHub Actions](https://imagej.net/develop/github-actions) page for configuration instructions, including how to migrate existing projects from Travis CI." %}
+{% include notice icon="note" content="SciJava projects now use Github Actions for CI. See the [GitHub Actions](/develop/github-actions) page for configuration instructions." %}
 
 {% include img src='logos/travis' align='right' width=150 caption='**Travis CI:** Build your code in the cloud!' %}