PR#1: Update README.md - fedora-qa/testdays

fedora-qa / testdays

#1 Update README.md

Opened 6 years ago by sumantrom. Modified 6 years ago

fedora-qa/ sumantrom/testdays master into main

Update README.md

Sumantro Mukherjee • 6 years ago

28f2650

README.md

file modified

+2 -2

		`@@ -2,12 +2,12 @@`

		`testdays is a small (at present) CLI for interacting with Fedora Test Day wiki pages, comparable to [relval][1] (which interacts with release validation test pages). Like relval, it uses the [python-wikitcms][1] module. Try it out:`

		`- testdays stats --release 25`
		`+ testdays stats --release 27`
		`testdays stats --filter nouveau --list-bugs`

		`## Source`

		- You can visit the [testdays project page on Pagure][2], and clone with `https://pagure.io/fedora-qa/testdays.git`. Tarballs are available for [download][3]. If you have its dependencies - `setuptools`, `wikitcms`, and, for pre-Python 2.7 systems, `argparse` - installed, you can run it directly from the git checkout as `./testdays.py`.
		+ You can visit the [testdays project page on Pagure][2], and clone with `https://pagure.io/fedora-qa/testdays.git`. Tarballs are available for [download][3]. If you have its dependencies - `setuptools`,`python-bugzilla`, `python-wikitcms`, and, for pre-Python 2.7 systems, `argparse` - installed, you can run it directly from the git checkout as `./testdays.py stats --release XY `.

		`## Repository`

sumantrom commented 6 years ago

package name update

adamwill commented 6 years ago

Thanks! Can you rebase this? Not sure why not, but it does not appear to be based on current master.

adamwill commented 6 years ago

Note, if you made your fork a while ago, your fork's master may not be up to date with upstream master. The strategy I usually follow to deal with this is, in my checkouts, to configure remotes for both the original upstream and the fork, and set the remote for the master branch to be the original upstream, not the fork, but push the PR branches to the fork. So my .git/config for a fork checkout looks like this:

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = ssh://git@pagure.io/forks/adamwill/fedora-kickstarts.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[remote "upstream"]
        url = ssh://git@pagure.io/fedora-kickstarts.git
        fetch = +refs/heads/*:refs/remotes/upstream/*
[branch "master"]
        remote = upstream
        merge = refs/heads/master
        rebase = true
[branch "1324623"]
        remote = origin
        merge = refs/heads/1324623
        rebase = true

adamwill commented 6 years ago

that way master branch in your checkout will be synced with upstream when you do git pull, and you can git rebase master your branches. The only gotcha is that if you git push the master branch, its remote gets reset to origin...