I am integrating travis-ci and I need to include the url to the build status points to my fork.
If I create a PR, they will have to change README.md and redirect that.
[![Build Status](https://travis-ci.org/FORK_USER/PROJECT.svg?branch=master)](https://travis-ci.org/FORK_USER/PROJECT)
How do I replace FORK_USER with something that works once the PR is merged?
You can't. Github markdown simply does not have any placeholder functionality for repos, users, etc. It's been a feature request for a long time too.
Related
My GitHub Pages site is built from the master branch, using my README.md. The top of my read-me file is directly below.
![pytest](https://github.com/preritdas/wooster-trading-systems/actions/workflows/pytest.yml/badge.svg)
![coverage-badge](tests/badge.svg)
![version](https://img.shields.io/badge/python-3.10-blue)
![maintenance-status](https://img.shields.io/badge/maintenance-actively--developed-brightgreen.svg)
![firebase](https://github.com/preritdas/wooster-trading-systems/actions/workflows/firebase-hosting-merge.yml/badge.svg)
![pages-build-deployment](https://github.com/preritdas/wooster-trading-systems/actions/workflows/pages/pages-build-deployment/badge.svg)
# :chart_with_upwards_trend: :robot: Wooster Systems :moneybag: :money_with_wings:
This looks just fine in the read-me inside the repository. Image below.
Unfortunately, the workflow status badges don't populate on the Jekyll GitHub Pages site. Specifically, the badges that come directly from GitHub don't show, but the rest do. The ones that don't show are tests, firebase deployment, and pages-build-deployment. A screenshot from the site is below.
I'm not sure why this is happening. My hunch is that it has to do with the fact that my repository is private, but what has me confused is the fact that the coverage badge comes from an SVG file directly in my private repository. This works fine on the site (possibly has to do with "artifacts", though I don't really understand the behavior). If the workflow badges are indeed private, how can I make them display on my site?
The only config file (or file that has anything to do with the GitHub Pages site) is my _config.yml, which has the following contents.
theme: jekyll-theme-cayman
plugins:
- jemoji
I installed added jemoji to support the emoji shortcode in my title, which works fine.
Any help appreciated.
Private repositories are not publicly visible. For security, any requests to them from an account without the right credentials will get a 404, so you can't guess which repositories exist.
Because the repository isn't available, your workflows and their results aren't public either. If you want a developer on your team to have the build status, invite them to your private repository. If you want your builds to be publicly visible, open source your repository.
It can be because this tags are alterated because of github actions, so they update and change on the Repository, Github pages treats different the information so this tags are nos updating when you are accessing the web page.
Live tags from Shields.io doesn't work properly on github pages.
I have made a pull request yesterday with the [WIP] tag and now my task is finished, I want the review so how will I remove that WIP tag from the Pull request to make that review ready from the organization repository on GitHub?
You need to click edit on the right of the PR when you open it, and then you can change the name, else the reviewer when merging into the main branch can change the name, and i suggest to use the git naming convention, to have a clean and organized history, using also gitmojis
I have created a github repo and deployed a simple HTML, CSS and JS website on it.
I want to create a github bot to automatically filter the pull request on the following basis:
If only the JS file is changed then the pull request is valid else it is invalid
Is it really possible to do that?
Thanks a lot for your help 😊
You could use a GitHub Action for that.
For instance, banyan/auto-label applies label based on file type.
In your case, fork that repository, and make your own GitHub Action in order to reject the PR if you detect a file whose extension is not the one set in your action.
A rejection ("mergeability of PR") can involve status check policy.
I wanted to fix some typos in a Microsoft documentation repo. I clicked on its New pull request button. That resulted in the following page being displayed:
As you can see, the green Create pull request button is disabled. How do I proceed from here? In other repos (such as for Amazon documentation), the process works differently, and I am able to directly create a pull request.
The common scenario of making such PRs looks like the following:
fork the repository http://prntscr.com/m7yhq0
make a new branch there with name like fix/several-typos http://prntscr.com/m7ytis
change a file and commit your changes to the branch (there should not be any difficulties)
go to the original repository, click New pull request and choose compare across forks http://prntscr.com/m7yih0
select necessary branches for PR and then the button Create pull request will be enabled.
Review your changes displayed below and click Create pull request
Hope that will help.
My project is a javascript doohicky, and so the entirety of the code is in javascript/html/css. In order to host the project, I created a github page.
Is there a way for the github page to "point to" the javascript and html in my main branch?
For example: My main branch has an index.html, is there a way to tell github to use this index.html as the gh page's index page?
Nope, no way to do that (Google Code can do that, AFAIK). The best you can do is:
a) make the gh-pages branch a branch of master (instead of resetting it) and just git rebase the gh-pages branch to the master branch every time you make an update to the master
or,
b) make the index.html page "smart" in the way that it is hosted on the gh-pages branch but is just an empty "shell" page which fetches its content from the master branch. I imagine this could be done via an iframe that covers the entire page and points to the index.html in the master branch (thus, effectively, the iframe becomes the page). Alternately, the webpage on the gh-pages branch could dynamically fetch content from the master branch via AJAX+GitHub API, and then inject the fetched content into itself (this is just for HTML content, since scripts and styles are easily injected via and tags).
I usually take approach a) for projects that are basically webapps.