GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - ent/bug: Template repository for reporting bugs

BranchesTags
Open more actions menu

Latest commit

 

History

17 Commits
17 Commits

Folders and files

NameName
Last commit message
Last commit date
ent
ent
 
 
README.md
README.md
 
 
bug_test.go
bug_test.go
 
 
docker-compose.yaml
docker-compose.yaml
 
 
go.mod
go.mod
 
 
go.sum
go.sum
 
 

Repository files navigation

Template Repository For Bug Reporting

Create a Repository From the Template

First and foremost, create a repository from this template repository (the one you're in now! 😊 ).

In order to do so, click 'Use this template' and create your repository.

Upload your desired code into the new repository.

If you happen to be a GitHub Teams or GitHub Enterprise customer you can alternatively choose to do so directly in the Codespace. Proceed to read if you want to learn how.

Once creating the desired repository, press . (period key) from the main repository page to switch over to dev mode.

Create a Codespace

Within dev mode, by clicking the 'Run and Debug' button you can create a new Codespace.

If you haven't already done so, you can import your code from your personal files by clicking File > Open File.

Inside Codespaces

Once you're inside Codespaces with your desired code, you can edit, run and debug it.

Editing

Let's say you want to edit the template ent/schema. For example, add a field named title to the User schema.

In ent/schema/user.go:

To generate this, we will run the command go generate ./ent in the Codespaces terminal.

To see if the command worked successfully, we can see that changes were made to files (files on the left-hand side became yellow, meaning changes were made that were not staged yet). Also, we can check inside ent/user/user.go if our field was added:

To learn more about working with ent, click here.

Saving Changes

If you have made changes to your code, by clicking on 'Source Control' you can directly stage, commit and push them into the repository.

By clicking the '+' you can stage your changes.

To commit the changes, enter a message and click the check mark. This button will automatically commit straight into the master branch.

Report a Bug

Now that your repository is ready, click here to submit an issue on the Ent repository.

When submitting your issue, a best practice would be to provide sufficient context, link to your new repository, and you're done!

About

Template repository for reporting bugs

Resources

Readme
Activity
Custom properties

Stars

11 stars

Watchers

1 watching

Forks

7 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.