Skip to content

Commit f604501

Browse files
authored
Revert "add guidelines (#6) (#8)" (#9)
This reverts commit 7bacb20.
1 parent 7bacb20 commit f604501

File tree

3 files changed

+2
-100
lines changed

3 files changed

+2
-100
lines changed

.github/scripts/sync-changes.js

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,7 @@ function createPutOptions(file, content) {
8585
'Content-Type': 'application/x-www-form-urlencoded; charset=UTF-8',
8686
'Accept': '*/*',
8787
'Api-Key': API_KEY,
88-
'Api-Username': API_USER,
89-
'skip_validations': true
88+
'Api-Username': API_USER
9089
}
9190
},
9291
payload

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ Would similarly be possible, but may be even more dangerous and are currently no
1414

1515
## How it works
1616

17-
This repo has a GitHub action that — upon commit to `main`identifies the files that changed in the HEAD commit. GitHub branch restrictions should ensure that only one commit lands at a time. These files are used as the slug names, with their contents as the content of the override and sent as a `PUT` to the site's API.
17+
This repo has a GitHub action that — upon commit to `main`uses the Discourse API to identify the files that changed in the HEAD commit. GitHub branch restrictions should ensure that only one commit lands at a time. These files are used as the slug names, with their contents as the content of the override.
1818

1919
The GitHub action does not perform the API call in pull requests; it only performs the API call upon commiting to `main`. All PRs must be carefully reviewed and if the action fails on `main`, then that commit should be reverted.

site_texts/guidelines_topic.body

Lines changed: 0 additions & 97 deletions
This file was deleted.

0 commit comments

Comments
 (0)