Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed formatting of "Updating" and "Adding" sections #194

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,13 +36,13 @@ workflows:
Note that if you want to hook onto deploy workflows, you'll need to deploy your `pantheon.yml` into an environment first. Likewise, if you are adding new operations or changing the script an operation will target, the deploy which contains those adjustments to `pantheon.yml` will not self-referentially exhibit the new behavior. Only subsequent deploys will be affected.

**When Updating:**
**pantheon.yml**: Updates will fire on the next sequential workflow, not post-deploy.
**scripts**: Updates will fire post-deploy.
**script location**: Updates will fire on next sequential workflow, not post-deploy.
- **`pantheon.yml`**: Updates will fire on the next sequential workflow, not post-deploy.
- **scripts**: Updates will fire post-deploy.
- **script location**: Updates will fire on next sequential workflow, not post-deploy.

**When Adding:**
**pantheon.yml**: Updates will fire on the next sequential workflow, not post-deploy.
**scripts**: Updates will fire on the next sequential workflow.
- **`pantheon.yml`**: Updates will fire on the next sequential workflow, not post-deploy.
- **scripts**: Updates will fire on the next sequential workflow.

## Security ##

Expand Down