rpms/vagrant-sshfs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The vagrant-sshfs rpms
36 commits 25 branches 0 tags 115 KiB
Find a file
Exact
Dusty Mabe 1fc992bfcb
 [packit] 1.3.5 upstream release 
Upstream tag: v1.3.5
Upstream commit: fa273792

Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
2020-06-29 01:53:44 -04:00
.gitignore [packit] 1.3.5 upstream release 2020-06-29 01:53:44 -04:00
.packit.yaml commit a packit.yaml file 2019-12-11 14:34:20 -05:00
README.md README: update with more specifics for packit 2020-03-15 21:46:55 -04:00
sources [packit] 1.3.5 upstream release 2020-06-29 01:53:44 -04:00
vagrant-sshfs.spec [packit] 1.3.5 upstream release 2020-06-29 01:53:44 -04:00

README.md

This repo can be controlled with packit.

You'll need a packit.yaml file created.

$ cat <<EOF > ~/.config/packit.yaml
debug: false
dry_run: false
authentication:
    github.com:
        token: XXX
    pagure:
        token: XXX
        instance_url: "https://src.fedoraproject.org"
EOF

The tokens come from:

Packit uses the master branch. Make sure the master branch in the local repo is up to date with latest upstream master. This can be tricky depending on if master tracks your fork or the upstream repo.

Then from this repo you can open a PR with:

$ packit propose-update

If that is not picking up the latest version for some reason you can specify the latest version with a syntax like:

$ packit propose-update https://github.com/dustymabe/vagrant-sshfs.git 1.3.4

You can kick off a build with:

$ packit build

Then sync to other branches and fedpkg build those too.