Adding functionality for Project Cards

[jpomfret]

Covers:

• List project cards
• Get a project card
• Create a project card
• Update a project card
• Delete a project card
• Move a project card

The tests don't run successfully without the Project code from PR #160, if you want I can rebase this branch with master once/if the core project code gets merged in?

[HowardWolosky]

Once again, you're rocking it with contributions. Thanks so much. 🎆

I do have some feedback for you to consider with this change. Again, thanks so much.

[HowardWolosky]

Can you resolve the merge conflict now in the .psd1 again (since a new conflict occurred now that the Columns work was merged in). Once resolved and I've verified a successful test pass, I'll get this one merged in, along with your documentation update. Then I'll rev the version number and publish out a new version.

Thanks for all your help!

[HowardWolosky]

After your merges, the psd1 is in that bad state again (every line changed). Can you please try the same fix again as you did on the other PR?

[jpomfret]

Alright - should be good now...

[HowardWolosky]

Perfect, thanks.

[HowardWolosky]

This is now available publicly in 0.12.0. Thanks so much for your contribution. 🎆

[HowardWolosky]

FYI @jpomfret - In my upcoming pipeline enabling change, I'm going to be changing the signature of New-GitHubProjectCard a little bit. Instead of having to specify ContentId and ContentType in order to associate an issue/pullrequest, users can directly either pass in the IssueId or PullRequestId (and the content type will be inferred based on which is provided). ParameterSets will be used to prevent both being passed in.

[jpomfret]

Makes sense to me, thanks for the heads up

[jpomfret]

Hey @HowardWolosky - has your change for ContentId --> IssueId/PullRequesetId made it to the PowerShell Gallery? Downloaded 0.14 today but it doesn't have this change in, even though I see it in this repo for version 0.14.

(Am finally finishing up a blog post on creating project/issue/cards with PowerShell so wanted to make sure I was accurate 😄)

[HowardWolosky]

Hi @jpomfret -- 0.14.0 is from 5/30/2020. There are tags in master that will sync you back to the state of the code for any given release. The change I discussed above is in master, but not part of any official release yet. There were a bunch of breaking changes that have been happening, and I have been trying to get all of them into a single release in order to help avoid having a series of releases with breaking changes.

The PR pipeline is just about flushed through of all the breaking changes. I can probably start working on the CHANGELOG update today so that I can release 0.15.0 within the next day or two.

[HowardWolosky]

@jpomfret -- Decided to do a little more work in the module to take advantage of all the breaking changes in the coming release. I think 0.15.0 will be released by this weekend.

As an FYI, an additional breaking change for your changes is that the Set-GitHub* commands will now be silent by default unless -PassThru is specified. See #276 for more info.

[jpomfret]

Sounds good! Sorry for the slow reply, looking forward to the new release. ☺️