* Fixed flaky tests
* Refactored ui_test commans-line, added documentation
* Attempt to build a workflow with cypress
* Fixed CI UX tests build
* Changed cyprss actions for pull-request
* Merged Cypress workflow into the regular PR target workflow
* Refactored Github workflows to include Cypress Tests
* Revert Ci build to pull_request_target
* Update CI badge in README.md after #3378
* Fix permissions issue with Coveralls token
* Run jobs for Java 8 and 14.
Temporarily re-hook the workflow to the pull_request event to test the setup.
* Publish coverage for master builds too
* Only keep JRE 8 and 14 in the build matrix.
For #3377.
* Run tests in GitHub Actions on each PR
* Attempt to fix Postgres configuration
* Set explicit password for Postgres on GitHub Actions
* Set explicit password for MySQL and MariaDB
* Fix credentials for postgres and mysql
* Fix duplicate id in GitHub workflow
* Fix creation of test_db on MySQL
* Revert back to GH Action MySQL service
* Populate initial test databases
* Fix syntax of workflow file
* Reorder steps to give more time for MySQL to boot
* Run MySQL database as a service, forward ports to config
* Reformat MySQL options
* Fix YAML syntax
* Add missing 'steps' field
* Fix connection to MySQL and Postgres
* Add back explicit database creation steps
* Force TCP/IP connection for postgres
* Remove explicit creation of test database for postgres
* Fix Postgres and Mariadb configs
* Fix parameter spelling for mariadb
* Display MariaDB test configuration
* Fix more inconsistent parameter names
* Fix more inconsistent parameter names
* Attempt to use Coveralls maven plugin instead of GH action
* Fix workflow file
* Enable submission to coveralls
* Supply coveralls token
* Remove Travis-specific configuration files
* Also update appveyor script after rename of SQL files
* Reintroduce packaging/test_pom.xml used by Appveyor
* Update filenames in appveyor.yml
As per GitHub Support, the only other thing left to do is also publish the FUNDING.yml file that links to the Organization itself to our OpenRefine repo so that folks visiting the repository directly will also see the Sponsor button.
Jack (GitHub Support)
Sep 1, 2020, 5:51 PM UTC
Hi Thad,
I ran this by our Sponsors product team, and they said that the link I shared https://docs.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository should have the correct information to add the Sponsors button to a repo. If you have any specific suggestions on how to improve it, we're definitely open to hearing how it can be improved or less confusing.
They said:
If they want the Sponsor button to show up in the OpenRefine/OpenRefine repo, then they will need to add a FUNDING.yml file under the .github/ directory on the default branch. The funding file should look something like:
github: OpenRefine
I hope this helps, but if we can further clarify, please let us know.
Best,
Jack
- Motivating change is removal of boilerplate text before description so we can see more of the description in hover previews.
- Also changes section headings from bolded to headings
- And combines OpenRefine version in same section as other versions
Make boilerplate/suggestions into comments so they don't show up in final issue if people forget to edit them out.
Add default labels to identify issues needing triage.
