https://github.com/backdrop-ops/forum.backdropcms.org
The Forum for BackdropCMS.org.
https://github.com/backdrop-ops/forum.backdropcms.org
backdrop backdropcms
Last synced: about 1 month ago
JSON representation
The Forum for BackdropCMS.org.
- Host: GitHub
- URL: https://github.com/backdrop-ops/forum.backdropcms.org
- Owner: backdrop-ops
- Created: 2017-01-19T22:59:38.000Z (about 9 years ago)
- Default Branch: main
- Last Pushed: 2025-07-15T16:28:55.000Z (8 months ago)
- Last Synced: 2025-07-16T12:19:48.855Z (8 months ago)
- Topics: backdrop, backdropcms
- Language: PHP
- Homepage: https://forum.backdropcms.org/
- Size: 21.9 MB
- Stars: 5
- Watchers: 12
- Forks: 11
- Open Issues: 42
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Forum: forum.backdropcms.org
============================
This is the repo for the Forum.BackdropCMS.org Forum.
Development
-----------
The forum site uses [Lando](https://docs.lando.dev/) for local development. Here
is how to get started:
* If you don't have Lando, download it: [Get Lando](https://lando.dev/download/)
* Fork this repository into your own GitHub account
* Download with git:
* `git clone git@github.com:[YOUR_USERNAME]/forum.backdropcms.org.git`
* Move into the project root:
* `cd forum.backdropcms.org`
* Start Lando
* `lando start`
* Download and import the DB
* `lando pull-db`
* Download and import the files
* `lando pull-files`
The database and files come from https://sanitize.backdropcms.org. This site is
protected by a username and password. You can request the credentials via
[Zulip](https://backdrop.zulipchat.com/login/).
Working on an Issue
-------------------
* Pick an issue from:
https://github.com/backdrop-ops/forum.backdropcms.org/issues
* Create a branch to work on
* `git checkout -b ISSUENUMBER/briefDescriptor`
* Replace ISSUENUMBER with your issue number
* Replace briefDescriptor w/ a description of your issue (no spaces)
* Do your work on your branch
* Add and commit your files
* Push up your branch
* `git push origin ISSUENUMBER/briefDescription`
* Submit a PR via the GitHub web UI
* Link your PR in the original issue
* Label the issue as `has PR`
* Request review by commenting on the issue and 'at' tagging the person(s)
that started the issue