Add the `workflow_dispatch` trigger to the Create Release Pull Request
workflow. This will allow us to more easily trigger the release Pull
Request if either 1) the scheduled run failed for whatever reason or 2)
an extra release is needed as per the DISCLAIMER.md.
You can read more about `workflow_dispatch` in the GitHub docs at:
https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch
* Remove files directly related to the website
Remove all the files directly related to the Jekyll-based website in
this repository. This includes the HTML, CSS and JS for the website, the
assets that can be found in the images/ folder, Jekyll-related files
(_config.yml, Gemfile, Gemfile.lock) and the CNAME file.
* Remove website-related configurations
Remove website-related files from ignore files, update the EditorConfig
configuration to remove any mention of website files, and update
.gitattributes to omit removed files.
* Update issue templates
Remove the issue templates for issues regarding the website and replace
it with a issue templates configuration file [1] that provides a link to
a the equivalent issue template in the simple-icons-website repository.
--
1. https://docs.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository
* Remove building website from verify workflow
* Remove mentions of website from Contributing Guidelines
* Remove mention of GitPod
I believe the main advantage of GitPod was that it allows you to preview
a contribution in the context of the website. Now that the website is no
longer in the repository this is not a thing anymore (unless someone
can configure GitPod to pull in the website from its repo), so I removed
any mention of it.
I'm open to reverting this change if contributors still want to use
GitPod.
* Add CI job for building the NodeJS package
* Restructure scripts/ directory
And update references to this scripts everywhere.
* Update names of file-level constants in bump-version.js
* Normalize quotes between all scripts
* Move "create-release.yml" scripts to scripts/release
* Move slugs table script to scripts/release
* Update relative path logic in update-slugs-table.js
* Add script to bump major version in README
On lines 29-32, we could alternatively use `replaceAll`, I opted not to
as it is not yet(?) part of an LTS release of NodeJS.
* Bump CDN version in README automatically for new releases
* Rename "bump-cdn-version.js" to "update-cdn-urls.js"
* Update names of file-level constants in update-cdn-urls.js
* Rename workflow setp for updating CDN URLs
* Rename packageJsonFile constant in update-cdn-urls
* Remove semver dependency
* Generalize update-cdn-urls script
* Update workflow names
Most importantly gives unique names to `create-release.yml` and
`merge-release.yml`.
Other than that, this attempts to improve and unify the names of all
workflows.
* Update release workflow names
Co-authored-by: Álvaro Mondéjar <mondejar1994@gmail.com>
Co-authored-by: Álvaro Mondéjar <mondejar1994@gmail.com>
* Auto assign to project workflow
* Remove redundant newline
* Update indentation in auto-assign-to-project.yml
Co-authored-by: Eric Cornelissen <ericornelissen@gmail.com>
* Remove .travis.yml reference from .gitattributes
* Minor refactoring of .svglintrc.js
- Remove unused variables
- Fix missing semi-colons
- Remove unneeded indentation
* Prevent error in clean command due to missing files
* Fix indentations
* Further improvements to Editorconfig and indentation
* Format YAML files
- Update indentation for array notation
- Normalize use of newlines
* Formalize website Ruby dependencies and installation process
* Improve Contributing Guidelines
* Add Gemfile.lock to .gitattributes
* Use 'ruby/setup-ruby' caching strategy
* Add link to documentation of 'bundler-cache'
* Split release workflow into two
Split the release workflow - which so far created and helped merging
release PRs - into a workflow for reating the release PR and one for
helping to merge it.
* Simplify merge-release.yml if-condition
Update release.yml, which is the workflow that creates release PRs and
merges them when approved, to use a Personal Access Token instead of
the standard GITHUB_TOKEN. I choose to name it RELEASE_TOKEN.
This change ensures that GitHub Actions workflows are triggered when
an action is performed by the Automated releases workflow. This is
needed because the publishing to NPM and the creation of a new GitHub
release should happen when there is a commit on `master`. If the release
PR is merged by the workflow using GITHUB_TOKEN, no GitHub Actions
workflows would be triggered.
Co-authored-by: Álvaro Mondéjar <mondejar1994@gmail.com>
* Add GitHub Actions workflow for verification
Add a GitHub Actions workflow file that does the verification of pushes
and pull requests. I.e., it runs the linters, runs the tests, and builds
the website. This workflow runs for all `pull_requests` and `push`es.
* Add GitHub Actions workflow for deployment
Add a GitHub Actions workflow file that does the deployment upon pushes
to master. Before actually deploying, the linters and test are ran, just
in case.
* Remove Travis CI configuration file
* Remove unnecessary quotes from existing workflows
* Add caching for "Build website" verification
* Update build badge in README
Co-authored-by: Álvaro Mondéjar <mondejar1994@gmail.com>
* Add Alexa ranks to GitHub Templates
* Add trailing newline to icon_request.md
* Remove excess space from icon_request.md
* Updates from review
* Remove choice between issue & rank
* Fix typo in issue template
Co-authored-by: Eric Cornelissen <ericornelissen@gmail.com>
* Improve wording in issue template and close last comment
Co-authored-by: Lucas Becker <runxel@users.noreply.github.com>
Co-authored-by: Eric Cornelissen <ericornelissen@gmail.com>
* Add workflow file to run PR labeler and corresponding configuration file
I'm using my personal fork of https://github.com/actions/labeler because
I could not any labeling action that checked whether a file was added or
changed (or removed).
* Fix typo in Labeler action configuration file
