Commit 94d5bd65 authored by Samuel Giddins's avatar Samuel Giddins

Merge pull request #5289 from CocoaPods/seg-update-issue-template

[Issue Template] Update for pod env & ask for project
parents 1f440c4a 881e464c
...@@ -22,12 +22,14 @@ ...@@ -22,12 +22,14 @@
> ℹ Please replace this with of what happened instead. > ℹ Please replace this with of what happened instead.
> e.g. Pod A is missing the subspec B for target C. > e.g. Pod A is missing the subspec B for target C.
## Podfile ## CocoaPods Environment
> ℹ Please paste the contents of your Podfile below. > ℹ Please replace this with the output of `pod env`.
> (e.g. via `cat Podfile | pbcopy`) > (e.g. via `pod env | pbcopy`)
> You can remove this hint then. > You can remove this hint then.
```ruby ## Project that demonstrates the issue
# Paste your Podfile contents HERE.
``` > ℹ Please link to a project we can download that reproduces the issue.
> You can delete this section if your issue is unrelated to build problems,
> i.e. it's only an issue with CocoaPods the tool.
...@@ -24,6 +24,7 @@ before_install: ...@@ -24,6 +24,7 @@ before_install:
before_script: before_script:
- bundle exec pod repo update --silent - bundle exec pod repo update --silent
- bundle exec pod env
script: script:
- bundle exec rake - bundle exec rake
......
...@@ -138,6 +138,9 @@ describe_cli 'pod' do ...@@ -138,6 +138,9 @@ describe_cli 'pod' do
# This was changed in a very recent git version # This was changed in a very recent git version
s.replace_pattern /git checkout -b <new-branch-name>/, 'git checkout -b new_branch_name' s.replace_pattern /git checkout -b <new-branch-name>/, 'git checkout -b new_branch_name'
# git sometimes prints this, but not always ¯\_(ツ)_/¯
s.replace_pattern /^\s*Checking out files.*done\.[\n]?/, ''
s.replace_path %r{ s.replace_path %r{
`[^`]*? # The opening backtick on a plugin path `[^`]*? # The opening backtick on a plugin path
([[[:alnum:]]_+-]+?) # The plugin name ([[[:alnum:]]_+-]+?) # The plugin name
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment