Hi guys, hi Elliot,
I would love to contribute to the advancement of the project but your workflow on github is unclear to me.
You have not tagged any versions since 4.1.8 or something. You only have a master branch and a multitude of pull requests. Is there a roadmap anywhere?
You should tag all releases and could use branches like
– 4.2 (for hotfixes)
– master (for the next feature release)
that way contributors knew where to send pull requests for bugfixes (current branch, e.g. 4.2) and for new features (master).
What do you think? Maybe you should publish some guidelines for pull requests/contributions. Demanding proper commenting of additions and/or changes so you can minimize the work on your side to evaluate them.
I for my part hate nothing more than a pull request of mine being “ignored”. A declined pull request with a short explanation is far better than one that is kept open indefinitely due to time issues.
I know that time is always an issue so please take this as constructive criticism.
For contributions to the docs you could open a “issues-only” repo on GitHub.
Or a separate docs repo. That would also allow you to have branches/tags to match the current code base. Folks could add docs for new features before they’re live and there’s no need to worry about which docs are live. When the code updates, the docs do too.
I’d help out here and there as I come across things but the barrier to entry is a little blurred.
The topic ‘GitHub workflow’ is closed to new replies.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!