abhijithvijayan / stargazed Goto Github PK

Checklist

• I checked that this is not an existing issue
• I gave clear steps to reproduce this issue
• I formatted all code samples correctly (if relevant)

Expected Behavior

A command like

stargazed --username almereyda --token of_sorts --sort --repository awesome-stars -w

sets up a GitHub repository, if not existing, and Action for updating the repository.

Current Behavior

1. Running the command without the repository existing does not create it with an initial commit and does not set the GitHub Action.
2. Running the command for a manually created repository does not create a commit and does not create a visible action in https://github.com/almereyda/awesome-stars/actions/new

Possible Solution

stargazed is able to fetch the repository's configuration If the repository does not yet exist, it is being created and set up with an initial commit plus GitHub Action. (Note the -w flag.)

Steps to Reproduce

1. Run the stargazed command above with your username and your personal access token.
2. Review the GitHub Actions

Context (Environment)

This is a Fedora 30, Node 10 environment.

Possible Implementation

It could be nice to have a CLI flag that can read the repository configuration and update on the status of an eventual integration.

The markdown linter, applies linting automatically on the template.md file when applied a change and saved.

The VScode I use, really messes this up and output produced by CLI is then ruined.

If there is any config that disables this auto lint, it might be useful.

export const validate = _options => {
^^^^^^

SyntaxError: Unexpected token export

I've been using this tool for past 2 months, but from few weeks, it's not working, I've been trying to debug things, but not able to figure it out the exact issue that's causing, would love to get it solved by you guys! Thanks! and I'm attaching the screenshot.

Checklist

• I checked that this is not an existing issue
• I gave clear steps to reproduce this issue

repo - https://github.com/abhisheknaiidu/nads

The README.md file generated in development somehow is included in the npm pack ed file, which increases the build size.

This file is ignored using .gitignore yet it is attached with the publishing package

Set up CI for running tests & also running CLI on different Node.js LTS versions

Preferred Travis

Use
[![Build Status](https://travis-ci.com/abhijithvijayan/stargazed.svg?branch=master)](https://travis-ci.com/abhijithvijayan/stargazed)

Checklist

Add contributing guidelines

Expected Behavior

make sure to ask to obey by the code of conduct file #17
and to have good behaviour to other contributors

As CLI has the template files within, it is better to notify user for the update if available.

https://github.com/zeit/update-check

Checklist

• I checked that this is not an existing issue
• I gave clear steps to reproduce this issue
• I formatted all code samples correctly (if relevant)

Expected Behavior

The pipe (|) gets escaped.

Current Behavior

The pipe (|) is not escaped, breaking the markdown of the table row.

Possible Solution

Escape the pipe

Steps to Reproduce

Live example (anti-xss):

Context

Original description of voku/anti-xss:

Detailed Description

Escape the pipe (|) to prevent it from breaking the markdown.

Possible Implementation

Currently only the list is being fetched with the -u flag.

The rest of the flags does nothing for now.

They are to be worked on soon enough.

Update configuration to use CI to run lint test along with yarn run test.

Use stars and owners name along.

Need List of Scopes that are required for TOKEN to make the stargazed CLI work like charm?

a general useful template
that has comments inside it saying to attach screenshots possible and also to check if such issue exists before creating

As eslint recommends to use an extension to the config file used, renaming .eslintrc to .eslintrc.json seems a good idea.

Please comment here first and then proceed to PR.

Complexity of some functions are way over the best and top.

As a solution to that, code splitting is necessary to tackle this.

Checklist

• Initial barebone
• Add unit tests for the commands offered by the cli

For merging PRs after CI(WIP) tests passed

Kodiak bot

with email [email protected]

Try

stargazed -u "phanirithvij"

- [DIGITAL Command Language](#digital-command language) is the output
The expected output should be

- [DIGITAL Command Language](#digital-command-language)

See https://github.com/abhijithvijayan/awesome-stars/blob/master/README.md#L26

• Jupyter Notebook (10)

To make it look like

sl. No | Name | Description | Author | Stars

Correction:

[C#](#c-1)
[C++](#c-2)
[Objective-C++](#objective-c-1)

If C# is missing, C++ will get #c-1 in the end trail of URL

Have to go through GitHub readme docs

Like

Automated publish: Sat Jan 18 03:32:36 UTC 2020

This format