kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity
capistrano/issue_template.md

22 lines
589 B
Markdown
Raw Normal View History

Update issue_template.md Remove line about "closing this issue"
2016-02-17 17:36:49 -05:00
**Important:** GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use [Stack Overflow](http://stackoverflow.com/questions/tagged/capistrano) for general questions. For more details, please see our [contribution policy](https://github.com/capistrano/capistrano/blob/master/CONTRIBUTING.md).
Create a first-pass issues template, so we can itterate on it in a PR GitHub apparently supports Issue Templates now, https://github.com/dear-github/dear-github/issues/125 - let's try one.
2016-02-17 13:04:01 -05:00
---
#### Steps to reproduce
Add doctor:variables, :environment, and :gems This adds various "doctor" tasks that can be used for troubleshooting. To see all the doctor output, run e.g. `cap production doctor`. This will print a report like this: ``` Environment Ruby ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14] Rubygems 2.6.2 Bundler 1.11.2 Command cap production doctor Gems capistrano 3.4.0 airbrussh 1.0.1 rake 10.5.0 (update available) sshkit 1.9.0 capistrano-bundler 1.1.4 capistrano-rails 1.1.6 Variables :application "myapp" :assets_prefix "assets" :assets_roles [:web] :branch "master" ... etc. ``` To obtain the variables information in particular, code has been added to audit the setting and fetching of variables. Variables set by Capistrano itself and its plugins are whitelisted, but others are "untrusted". If a variable is untrusted and it seems like it is never used, then `doctor:variables` will print a warning (include source location) for that variable name, like this: ``` :copy_strategy is not a recognized Capistrano setting (config/deploy.rb:14) ``` Finally, the RubyGems API is used to check the remote gem repository to see if any newer versions of Capistrano gems are available (this is gracefully skipped if there is no network connection). Any outdated gems will be indicated in the `doctor:gems` output.
2016-03-09 20:13:17 -05:00
Create a first-pass issues template, so we can itterate on it in a PR GitHub apparently supports Issue Templates now, https://github.com/dear-github/dear-github/issues/125 - let's try one.
2016-02-17 13:04:01 -05:00
1. Lorem.
2. Ipsum..
3. Dolor...
#### Expected behaviour
Add doctor:variables, :environment, and :gems This adds various "doctor" tasks that can be used for troubleshooting. To see all the doctor output, run e.g. `cap production doctor`. This will print a report like this: ``` Environment Ruby ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14] Rubygems 2.6.2 Bundler 1.11.2 Command cap production doctor Gems capistrano 3.4.0 airbrussh 1.0.1 rake 10.5.0 (update available) sshkit 1.9.0 capistrano-bundler 1.1.4 capistrano-rails 1.1.6 Variables :application "myapp" :assets_prefix "assets" :assets_roles [:web] :branch "master" ... etc. ``` To obtain the variables information in particular, code has been added to audit the setting and fetching of variables. Variables set by Capistrano itself and its plugins are whitelisted, but others are "untrusted". If a variable is untrusted and it seems like it is never used, then `doctor:variables` will print a warning (include source location) for that variable name, like this: ``` :copy_strategy is not a recognized Capistrano setting (config/deploy.rb:14) ``` Finally, the RubyGems API is used to check the remote gem repository to see if any newer versions of Capistrano gems are available (this is gracefully skipped if there is no network connection). Any outdated gems will be indicated in the `doctor:gems` output.
2016-03-09 20:13:17 -05:00
Create a first-pass issues template, so we can itterate on it in a PR GitHub apparently supports Issue Templates now, https://github.com/dear-github/dear-github/issues/125 - let's try one.
2016-02-17 13:04:01 -05:00
Tell us what should happen
#### Actual behaviour
Add doctor:variables, :environment, and :gems This adds various "doctor" tasks that can be used for troubleshooting. To see all the doctor output, run e.g. `cap production doctor`. This will print a report like this: ``` Environment Ruby ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14] Rubygems 2.6.2 Bundler 1.11.2 Command cap production doctor Gems capistrano 3.4.0 airbrussh 1.0.1 rake 10.5.0 (update available) sshkit 1.9.0 capistrano-bundler 1.1.4 capistrano-rails 1.1.6 Variables :application "myapp" :assets_prefix "assets" :assets_roles [:web] :branch "master" ... etc. ``` To obtain the variables information in particular, code has been added to audit the setting and fetching of variables. Variables set by Capistrano itself and its plugins are whitelisted, but others are "untrusted". If a variable is untrusted and it seems like it is never used, then `doctor:variables` will print a warning (include source location) for that variable name, like this: ``` :copy_strategy is not a recognized Capistrano setting (config/deploy.rb:14) ``` Finally, the RubyGems API is used to check the remote gem repository to see if any newer versions of Capistrano gems are available (this is gracefully skipped if there is no network connection). Any outdated gems will be indicated in the `doctor:gems` output.
2016-03-09 20:13:17 -05:00
Create a first-pass issues template, so we can itterate on it in a PR GitHub apparently supports Issue Templates now, https://github.com/dear-github/dear-github/issues/125 - let's try one.
2016-02-17 13:04:01 -05:00
Tell us what happens instead
#### Your configuration
Add doctor:variables, :environment, and :gems This adds various "doctor" tasks that can be used for troubleshooting. To see all the doctor output, run e.g. `cap production doctor`. This will print a report like this: ``` Environment Ruby ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14] Rubygems 2.6.2 Bundler 1.11.2 Command cap production doctor Gems capistrano 3.4.0 airbrussh 1.0.1 rake 10.5.0 (update available) sshkit 1.9.0 capistrano-bundler 1.1.4 capistrano-rails 1.1.6 Variables :application "myapp" :assets_prefix "assets" :assets_roles [:web] :branch "master" ... etc. ``` To obtain the variables information in particular, code has been added to audit the setting and fetching of variables. Variables set by Capistrano itself and its plugins are whitelisted, but others are "untrusted". If a variable is untrusted and it seems like it is never used, then `doctor:variables` will print a warning (include source location) for that variable name, like this: ``` :copy_strategy is not a recognized Capistrano setting (config/deploy.rb:14) ``` Finally, the RubyGems API is used to check the remote gem repository to see if any newer versions of Capistrano gems are available (this is gracefully skipped if there is no network connection). Any outdated gems will be indicated in the `doctor:gems` output.
2016-03-09 20:13:17 -05:00
Paste Capistrano's `doctor` output here (`cap <stage> doctor`):
Copy permalink