Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
form-processor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mattwire
form-processor
Commits
886bfcc4
Commit
886bfcc4
authored
4 years ago
by
jaapjansma
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
0cd44568
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+19
-3
19 additions, 3 deletions
README.md
with
19 additions
and
3 deletions
README.md
+
19
−
3
View file @
886bfcc4
# form-processor

The form processor extension gives you the ability to define business logic for handling form submissions.
A form submission could come from the CiviMRF, external system or just a direct submission.
[
See **
wiki
** for more information
](
https://
lab
.civicrm.org/
jaapjansma/
form
-
procesor
-designer/wikis/home
)
.
[
See **
docs
** for more information
](
https://
docs
.civicrm.org/formproces
s
or
/en/latest/
)
.
The extension is licensed under
[
AGPL-3.0
](
LICENSE.txt
)
.
## Contributing
Feel free to contribute to this extension. Create a Merge Request and also add a little description to CHANGELOG.md of what you have changed
## Releasing Process
When one of the admins think it is time to relase a new version they might do so. You can also ask them to release a new version.
Usually this when the release is being tested and put in production.
For admins creating a release those are the steps to follow:
1.
Update info.xml to reflect the new version number and release date
2.
Remove the 'not yet released' from CHANGELOG.md
3.
Copy the changes
4.
Go to tags, create a new tag and paste the changes
5.
After that update info.xml to add a new version number ending with _-dev_
6.
Update changelog add a heading for the new version with the text _not yet released_
## Requirements
*
PHP v5.4+
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment