You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,16 +89,9 @@ The broad steps are:
89
89
##### Resolving Patch Errors
90
90
91
91
The auto-generated method files may drift overtime e.g. new arguments may be added or descriptions changed. Since previous patches were based on the older auto-generated files, git may be unable to apply them to the new files. Resolving them requires some good ol' splicing:
92
-
1. Comment out the patching code in `lib/tasks/web.rake`:
93
-
```ruby
94
-
# Dir.glob("lib/slack/web/api/patches/#{group}*.patch").sort.each do |patch|
95
-
# puts "- patching #{patch}"
96
-
# system("git apply #{patch}") || raise('failed to apply patch')
97
-
# end
98
-
```
99
-
2. Run `rake slack:api:update` to create the raw auto-generated files. Commit the files that you are updating, so we can run `git diff` later.
100
-
3. Go through the old patches for the files (e.g. in `lib/slack/web/api/patches/chat.1.patch`), copying code into the new files.
101
-
4. Continue with Step 2 [above](#patching-slack-web-api).
92
+
1. Run `rake slack:api:update SKIP_PATCH=true` to create the raw auto-generated files. Commit the files that you are updating, so we can run `git diff` later.
93
+
2. Go through the old patches for the files (e.g. in `lib/slack/web/api/patches/chat.1.patch`), copying code into the new files.
94
+
3. Continue with Step 2 [above](#patching-slack-web-api).
0 commit comments