github_auth48_experiment
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| github_auth48_experiment [2022/07/20 21:19] – RFC 8446 info moved to github_exp_8446 jmahoney | github_auth48_experiment [2026/02/12 05:44] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| - | ==== Work Flow in 2020-2021 ==== | + | Please |
| - | + | ||
| - | The authors and editor agreed to use the GitHub Pull Request work flow: | + | |
| - | + | ||
| - | - The authors answer the AQ in the comments of the issue (e.g., | + | |
| - | - The authors indicate that an issue is ready for editor attention by labeling the issue " | + | |
| - | - The editor creates a branch off the rfced branch to address the issue. | + | |
| - | - The editor makes edits in that branch. | + | |
| - | - The editor commits changes. | + | |
| - | - The editor creates a Pull Request (PR) to submit the changes to the repo (e.g., [[https:// | + | |
| - | - The authors review the PR: | + | |
| - | - If the PR is accepted, the authors merge the changes to the rfced branch, which closes the issue. | + | |
| - | - If the PR is rejected, the editor makes changes to the current branch and resubmits the PR. | + | |
| - | - Repeat for the other issues. | + | |
| - | + | ||
| - | The authors and the editor set up notifications so that many of these steps automatically generated emails to involved parties (assigning/ | + | |
| - | + | ||
| - | ==== Feedback in 2020-2021 ==== | + | |
| - | + | ||
| - | * See [[github_exp_2021_feedback]] for notes from the RFC Editor. | + | |
github_auth48_experiment.1658351998.txt.gz · Last modified: (external edit)
