Skip to content
This repository has been archived by the owner on Feb 4, 2025. It is now read-only.

Rename service files to content-service #72

Merged
merged 1 commit into from
Jun 19, 2020

Conversation

joselsegura
Copy link
Collaborator

Description

Simple PR, only rename entry point files to something more descriptive

Type of change

  • Refactor (refactoring code, removing useless files)

Testing steps

Regular CI

Copy link

@Serhii1011010 Serhii1011010 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, but usually underscore is used to split words in go file names.

Copy link
Collaborator

@tisnik tisnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not :) Thank you

@codecov-commenter
Copy link

Codecov Report

Merging #72 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #72   +/-   ##
=======================================
  Coverage   80.49%   80.49%           
=======================================
  Files           8        8           
  Lines         323      323           
=======================================
  Hits          260      260           
  Misses         49       49           
  Partials       14       14           
Impacted Files Coverage Δ
content-service.go 48.52% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f119cd6...39f5e73. Read the comment docs.

@joselsegura joselsegura merged commit a419637 into RedHatInsights:master Jun 19, 2020
@joselsegura joselsegura deleted the rename_service branch June 19, 2020 15:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants