view release on metacpan or search on metacpan
lib/Git/Code/Review/Command/config.pm view on Meta::CPAN
';',
';[global]',
'; server = imap.mailserver.com',
'; port = 993',
'; ssl = 1',
'; credentials-file = /etc/code-review/sox_code_review_email.conf',
'; folder = INBOX',
'; auto-approve = 1',
],
'notification.config' => [
"; Notification Configuration for audit",
view release on metacpan or search on metacpan
lib/Git/Github/Creator.pm view on Meta::CPAN
DEBUG( "Project homepage is [$homepage]" );
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# Get to Github
my $credentials = do {
if( defined $Config{'api-token'} ) {
my $hash = {
access_token => $Config{'api-token'}
};
}
lib/Git/Github/Creator.pm view on Meta::CPAN
else {
my $hash = {},
}
};
my $github = Net::GitHub::V3->new( %$credentials );
DEBUG( "Got to GitHub" );
die "Exiting since you are debugging\n" if $Config{debug};
DEBUG( "Logged in" );
view release on metacpan or search on metacpan
lib/Git/Hooks/CheckJira.pm view on Meta::CPAN
# These users are exempt from all checks
admin = joe molly
[githooks "checkjira"]
# Configure the URL and the admin credentials to interact with the Jira
# server.
jiraurl = https://jira.example.net
jirauser = jiradmin
jirapass = my-secret
view release on metacpan or search on metacpan
# Claude Code — commit: skills/, agents/, hooks/, settings.json
# Ignore: local overrides, credentials, session data
# Tracked: shared config & extensibility
!/.claude/
.claude/*
!.claude/settings.json
# Local overrides (machine-specific)
.claude/*.local.*
.claude/local/
# Credentials & session state (never track)
.claude/.credentials.json
.claude/statsig/
.claude/todos/
.claude/projects/
# Perl / Dist::Zilla distribution
view release on metacpan or search on metacpan
lib/Git/Megapull/Source/Github.pm view on Meta::CPAN
This source will probably be broken out into its own dist in the future.
=head1 TODO
* add means to include/exclude private repos
* add means to use alternate credentials
* investigate using Github::API
=head1 AUTHOR
Ricardo SIGNES <rjbs@cpan.org>
view release on metacpan or search on metacpan
lib/Git/Native.pm view on Meta::CPAN
}
return $r;
}
# clone($url, $local_path) - non-bare only for now.
# Auth via credentials => sub {...} not yet plumbed; the clone_options
# struct embeds a fetch_options whose callback offset we'd need to probe
# per libgit2 version. Bare clones go through init+fetch+HEAD instead -
# the offset of `bare` is past two large embedded structs and isn't
# stable across libgit2 versions worth pinning here.
sub clone {
view release on metacpan or search on metacpan
lib/Git/Raw/Cred.pm view on Meta::CPAN
use strict;
use warnings;
=head1 NAME
Git::Raw::Cred - Git credentials class
=head1 VERSION
version 0.90
=head1 DESCRIPTION
A L<Git::Raw::Cred> object is used to store credentials.
B<WARNING>: The API of this module is unstable and may change without warning
(any change will be appropriately documented in the changelog).
=head1 METHODS
view release on metacpan or search on metacpan
lib/Git/Reduce/Tests.pm view on Meta::CPAN
=item * Purpose
Push the reduced branch to the remote specified in the C<--remote> option,
which defaults to C<origin>. This, of course, assumes that the user has
permission to perform that action, has proper credentials such as SSH keys,
etc.
=item * Arguments
$self->push_to_remote($reduced_branch);
view release on metacpan or search on metacpan
=item credential( CREDENTIAL_HASHREF [, OPERATION ] )
=item credential( CREDENTIAL_HASHREF, CODE )
Executes C<git credential> for a given set of credentials and specified
operation. In both forms C<CREDENTIAL_HASHREF> needs to be a reference to
a hash which stores credentials. Under certain conditions the hash can
change.
In the first form, C<OPERATION> can be C<'fill'>, C<'approve'> or C<'reject'>,
and function will execute corresponding C<git credential> sub-command. If
it's omitted C<'fill'> is assumed. In case of C<'fill'> the values stored in
view release on metacpan or search on metacpan
lib/GitHub/Apps/Auth.pm view on Meta::CPAN
private_key => "<filename>",
app_id => <app_id>,
installation_id => <installation_id>
);
Constructs an instance of C<GitHub::Apps::Auth> from credentials.
=head3 parameters
=head4 private_key
view release on metacpan or search on metacpan
lib/GitHub/Authorization.pm view on Meta::CPAN
=head3 On failure/error...
On failure, we confess() our sins:
Failed: 401/Unauthorized / Bad credentials ...
That is, we L<Carp/confess> with the status code, status message, and the
message returned from GitHub itself.
=head2 legal_scopes
view release on metacpan or search on metacpan
lib/GitHub/RSS.pm view on Meta::CPAN
=item *
B<token_file> - name and path of the JSON-format token file containing the
GitHub API token By default, that file is searched for under the name
C<github.credentials> in C<.>, C<$ENV{XDG_DATA_HOME}>, C<$ENV{USERPROFILE}>
and C<$ENV{HOME}>.
=cut
has 'token_file' => (
lib/GitHub/RSS.pm view on Meta::CPAN
$ENV{XDG_DATA_HOME},
$ENV{USERPROFILE},
$ENV{HOME}
) {
next unless defined $candidate_dir;
if( -f "$candidate_dir/github.credentials" ) {
$token_file = "$candidate_dir/github.credentials";
last
};
};
return $token_file
view release on metacpan or search on metacpan
author/header.pm view on Meta::CPAN
Note that this distribution also includes the L<gitlab-api-v3> command-line
interface (CLI).
=head1 CREDENTIALS
Authentication credentials may be defined by setting either the L</token>,
the L</login> and L</password>, or the L</email> and L</password> arguments.
When the object is constructed the L</login>, L</email>, and L</password>
arguments are used to call L</session> to generate a token. The token is
saved in the L</token> attribute, and the login/email/password arguments
are discarded.
If no credentials are supplied then the client will be anonymous and greatly
limited in what it can do with the API.
=head2 CONSTANTS
Several values in the GitLab API require looking up the numeric value
view release on metacpan or search on metacpan
author/header.pm view on Meta::CPAN
C<git diff 72e384775c9570f60f8ef68dee3a1eecd347fb69..HEAD -- author/sections/>
=head2 Credentials
Authentication credentials may be defined by setting either the L</access_token>
or L</private_token> arguments.
If no credentials are supplied then the client will be anonymous and greatly
limited in what it can do with the API.
Extra care has been taken to hide the token arguments behind closures. This way,
if you dump your api object, your tokens won't accidentally leak into places you
don't want them to.
view release on metacpan or search on metacpan
lib/DBD/Gofer/Transport/http.pm view on Meta::CPAN
timeout => $self->go_timeout, # undef by default
keep_alive => $CONN_CACHE, # sets total_capacity of LWP::ConnCache
env_proxy => 1, # XXX
);
$useragent->agent(join "/", __PACKAGE__, $DBI::VERSION, $VERSION);
#$useragent->credentials( $netloc, $realm, $uname, $pass ); XXX
$useragent->parse_head(0); # don't parse html head
$useragent;
};
my $content = $frozen_request;
view release on metacpan or search on metacpan
examples/oauth/authenticate_with_web_flow.pl view on Meta::CPAN
$cgi->end_html;
}
}
# This starts the OAuth2 authentication process where the user will be
# prompted to log in with the credentials that have access to their AdWords
# account. During this process, the user has to confirm that permission is
# granted for our application to access AdWords using their credentials.
sub resp_login {
my $cgi = shift;
return if !ref $cgi;
# Get AdWords Client, ~/adwords.properties will be read.
view release on metacpan or search on metacpan
examples/account_management/create_customer.pl view on Meta::CPAN
# limitations under the License.
#
# This example illustrates how to create a new customer under a given manager
# account.
#
# Note: This example must be run using the credentials of a Google Ads manager
# account. By default, the new account will only be accessible via the manager
# account.
use strict;
use warnings;
examples/account_management/create_customer.pl view on Meta::CPAN
# Don't run the example if the file is being included.
if (abs_path($0) ne abs_path(__FILE__)) {
return 1;
}
# Get Google Ads Client, credentials will be read from ~/googleads.properties.
my $api_client = Google::Ads::GoogleAds::Client->new();
# By default examples are set to die on any server returned fault.
$api_client->set_die_on_faults(1);
examples/account_management/create_customer.pl view on Meta::CPAN
=head1 DESCRIPTION
This example illustrates how to create a new customer under a given manager account.
Note: This example must be run using the credentials of a Google Ads manager account.
By default, the new account will only be accessible via the manager account.
=head1 SYNOPSIS
create_customer.pl [options]