Skip to content

Commit

Permalink
Fixes based on addition of acceptable-values
Browse files Browse the repository at this point in the history
Signed-off-by: Anthony Emengo <aemengo@vmware.com>
  • Loading branch information
Anthony Emengo committed Jul 22, 2021
1 parent d3e6575 commit 8d09f74
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 5 deletions.
3 changes: 1 addition & 2 deletions 0000-template.md
Expand Up @@ -3,8 +3,7 @@
- Name: (fill in the feature name: My Feature)
- Start Date: (fill in today's date: YYYY-MM-DD)
- Author(s): (Github usernames)
<!-- Acceptable values: Approved, On Hold, Draft` -->
- Status: Draft
- Status: Draft <!-- Acceptable values: Approved, On Hold, Draft -->
- RFC Pull Request: (leave blank)
- CNB Pull Request: (leave blank)
- CNB Issue: (leave blank)
Expand Down
2 changes: 1 addition & 1 deletion merge-rfc.sh
Expand Up @@ -75,7 +75,7 @@ TARGET=${SOURCE//0000/$(printf "%04d" "${ID}")}

sed -i '' "s|- RFC Pull Request:.*|- RFC Pull Request: [rfcs#${PR}](https://github.com/buildpacks/rfcs/pull/${PR})|" "${SOURCE}"
sed -i '' "s|- CNB Issue:.*|- CNB Issue: $issues|" "${SOURCE}"
sed -i '' "s,- Status:.*,- Status: **Approved** | On Hold," "${SOURCE}"
sed -i '' "s|- Status:.*|- Status: Approved|" "${SOURCE}"
git mv "${SOURCE}" "${TARGET}"
git add "${TARGET}"
git commit --signoff --message "RFC ${ID}
Expand Down
4 changes: 2 additions & 2 deletions text/0000-add-status-field.md
Expand Up @@ -3,7 +3,7 @@
- Name: Add Status to RFC Metadata
- Start Date: 2021-07-14
- Author(s): @aemengo, @ekcasey
- Status: Approved | On Hold
- Status: Draft <!-- Acceptable values: Approved, On Hold, Draft -->
- RFC Pull Request: (leave blank)
- CNB Pull Request: (leave blank)
- CNB Issue: (leave blank)
Expand Down Expand Up @@ -33,7 +33,7 @@ The acceptable values are distinguished in the following ways:
- **Approved**: The Core team has approved the RFC and is accepting PRs for its implementation.
- **On Hold**: The Core team has approved the RFC, but PRs are currently not being accepted for its implementation. A reason must be provided in the RFC.

The `Status:` field does not intend to reflect states that are already implied by the RFC process. Examples including: *Draft*, *In Review*, *Closed*, etc.
The `Status:` field does not intend to reflect states that are already implied by the RFC process. Examples including: *In Review*, *Closed*, etc.

# How it Works
[how-it-works]: #how-it-works
Expand Down

0 comments on commit 8d09f74

Please sign in to comment.