mirror of
https://github.com/zoriya/octokit.net.git
synced 2026-05-27 16:42:03 +00:00
73feecefb3
* Add convention test to ensure 'Url' properties are of type string Closes #1582 * Change 'Url' properties from Uri to string Global Find/Replace FTW! * fix compilation errors in the integration tests project * Extend 'Url' properties type check to request models * Stick to convention tests naming convention * Remove unused using directives in models Changing from `Uri` to `string` means the `using System;` directive was not needed anymore in some files * Update exception message wording * empty commit to trigger a new build - hopefully Travis passes * add convention test to ensure request models have Uri 'Url' properties * make request models 'Url' properties Uri fix typo in convention test name * revert some request models 'Url' properties as `string` see https://github.com/octokit/octokit.net/pull/1585#issuecomment-297186728 * Change test so that all model types must have 'Url' properties of type string - Filter test input to only get types which have 'Url' properties - Merge response and request model types tests into one - Unparameterize the exception since we only check for the string type now * Fix string.Format tokens If this PR doesn't get rebased, it'll be my wall of shame FOREVER! * and then it's even more embarrassing when the commit message says rebased but you really meant squashed * Remove exclusion of `Release` from request models
43 lines
1.3 KiB
C#
43 lines
1.3 KiB
C#
using System.Diagnostics;
|
||
using System.Globalization;
|
||
|
||
namespace Octokit
|
||
{
|
||
/// <summary>
|
||
/// Used to create a new commit status.
|
||
/// </summary>
|
||
[DebuggerDisplay("{DebuggerDisplay,nq}")]
|
||
public class NewCommitStatus
|
||
{
|
||
/// <summary>
|
||
/// The state of the commit.
|
||
/// </summary>
|
||
public CommitState State { get; set; }
|
||
|
||
/// <summary>
|
||
/// URL associated with this status. GitHub.com displays this URL as a link to allow users to easily see the
|
||
/// ‘source’ of the Status. For example, if your Continuous Integration system is posting build status,
|
||
/// you would want to provide the deep link for the build output for this specific sha.
|
||
/// </summary>
|
||
public string TargetUrl { get; set; }
|
||
|
||
/// <summary>
|
||
/// Short description of the status.
|
||
/// </summary>
|
||
public string Description { get; set; }
|
||
|
||
/// <summary>
|
||
/// A string label to differentiate this status from the status of other systems.
|
||
/// </summary>
|
||
public string Context { get; set; }
|
||
|
||
internal string DebuggerDisplay
|
||
{
|
||
get
|
||
{
|
||
return string.Format(CultureInfo.InvariantCulture, "Description: {0}, Context: {1}", Description, Context);
|
||
}
|
||
}
|
||
}
|
||
}
|